[lwip-commits] [SCM] UNNAMED PROJECT branch, master, updated. d7a951996b95f2884e20b5b327d345faaedcf4f0

[Simon Goldschmidt]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "UNNAMED PROJECT".

The branch, master has been updated
       via  d7a951996b95f2884e20b5b327d345faaedcf4f0 (commit)
       via  38bfe5050847509c2ba8883c004f0c3f6383a155 (commit)
      from  a70567e74f510bfe6693bf8ef014be5d742df6f2 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit d7a951996b95f2884e20b5b327d345faaedcf4f0
Author: Simon Goldschmidt <address@hidden>
Date:   Sat Jan 18 22:41:52 2014 +0100

    Updated CHANGELOG

commit 38bfe5050847509c2ba8883c004f0c3f6383a155
Author: Stathis Voukelatos <address@hidden>
Date:   Thu Jan 17 16:52:47 2013 +0000

    Fixed size calculation in MALLOC memory pool creation macro.
    
    The LWIP_MALLOC_MEMPOOL macro needs to use the aligned size of the
    memp_malloc_helper structure, since mem_alloc() uses it to calculate
    the required pool element size. If LWIP_MEM_ALIGN_SIZE(x) is redefined
    to align to something larger than 4, then in some cases
    the current code can lead to unexpected mem_alloc() failures.
    For example:
        #define LWIP_MEM_ALIGN_SIZE(size)       (((size) + 31) & ~31)
    and the largest MALLOC pool is of size 60 bytes, e.g.:
        #define LWIP_MALLOC_MEMPOOL(256, 60)
    then the following call:
        mem_malloc(58)
    will cause an assertion.

-----------------------------------------------------------------------

Summary of changes:
 CHANGELOG                   |    4 ++++
 src/include/lwip/memp_std.h |    2 +-
 2 files changed, 5 insertions(+), 1 deletions(-)


hooks/post-receive
-- 
UNNAMED PROJECT