The patch titled Subject: mm: move slabinfo.c to tools/vm has been added to the -mm tree. Its filename is move-slabinfoc-to-tools-vm.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: Dave Young <dyoung@xxxxxxxxxx> Subject: mm: move slabinfo.c to tools/vm We have tools/vm/ folder for vm tools, so move slabinfo.c from tools/slub/ to tools/vm/ Signed-off-by: Dave Young <dyoung@xxxxxxxxxx> Cc: Wu Fengguang <fengguang.wu@xxxxxxxxx> Acked-by: Christoph Lameter <cl@xxxxxxxxx> Cc: Pekka Enberg <penberg@xxxxxxxxxxxxxx> Cc: Frederic Weisbecker <fweisbec@xxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- tools/vm/Makefile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff -puN tools/vm/Makefile~move-slabinfoc-to-tools-vm tools/vm/Makefile --- a/tools/vm/Makefile~move-slabinfoc-to-tools-vm +++ a/tools/vm/Makefile @@ -3,9 +3,9 @@ CC = $(CROSS_COMPILE)gcc CFLAGS = -Wall -Wextra -all: page-types +all: page-types slabinfo %: %.c $(CC) $(CFLAGS) -o $@ $^ clean: - $(RM) page-types + $(RM) page-types slabinfo _ Subject: Subject: mm: move slabinfo.c to tools/vm Patches currently in -mm which might be from dyoung@xxxxxxxxxx are linux-next.patch loop-zero-fill-bio-instead-of-return-eio-for-partial-read.patch selftests-launch-individual-selftests-from-the-main-makefile.patch move-page-typesc-from-documentation-to-tools-vm.patch move-slabinfoc-to-tools-vm.patch move-hugepage-test-examples-to-tools-testing-selftests-vm.patch move-hugepage-test-examples-to-tools-testing-selftests-vm-fix.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