Subject: + mm-get-rid-of-__gfp_kmemcg-fix.patch added to -mm tree To: sfr@xxxxxxxxxxxxxxxx,vdavydov@xxxxxxxxxxxxx From: akpm@xxxxxxxxxxxxxxxxxxxx Date: Wed, 16 Apr 2014 12:16:22 -0700 The patch titled Subject: mm: get rid of __GFP_KMEMCG fix has been added to the -mm tree. Its filename is mm-get-rid-of-__gfp_kmemcg-fix.patch This patch should soon appear at http://ozlabs.org/~akpm/mmots/broken-out/mm-get-rid-of-__gfp_kmemcg-fix.patch and later at http://ozlabs.org/~akpm/mmotm/broken-out/mm-get-rid-of-__gfp_kmemcg-fix.patch Before you just go and hit "reply", please: a) Consider who else should be cc'ed b) Prefer to cc a suitable mailing list as well c) Ideally: find the original patch on the mailing list and do a reply-to-all to that, adding suitable additional cc's *** Remember to use Documentation/SubmitChecklist when testing your code *** The -mm tree is included into linux-next and is updated there every 3-4 working days ------------------------------------------------------ From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> Subject: mm: get rid of __GFP_KMEMCG fix export kmalloc_order() to modules Signed-off-by: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> Cc: Vladimir Davydov <vdavydov@xxxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- mm/slab_common.c | 1 + 1 file changed, 1 insertion(+) diff -puN mm/slab_common.c~mm-get-rid-of-__gfp_kmemcg-fix mm/slab_common.c --- a/mm/slab_common.c~mm-get-rid-of-__gfp_kmemcg-fix +++ a/mm/slab_common.c @@ -584,6 +584,7 @@ void *kmalloc_order(size_t size, gfp_t f kmemleak_alloc(ret, size, 1, flags); return ret; } +EXPORT_SYMBOL(kmalloc_order); #ifdef CONFIG_TRACING void *kmalloc_order_trace(size_t size, gfp_t flags, unsigned int order) _ Patches currently in -mm which might be from sfr@xxxxxxxxxxxxxxxx are mm-get-rid-of-__gfp_kmemcg-fix.patch lib-scatterlist-make-arch_has_sg_chain-an-actual-kconfig-fix-3.patch kernel-forkc-export-kernel_thread-to-modules.patch -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html