The patch titled Subject: Documentation/sysctl/vm.txt: update __vm_enough_memory()'s path has been added to the -mm tree. Its filename is update-documents-__vm_enough_memory-function-path.patch This patch should soon appear at http://ozlabs.org/~akpm/mmots/broken-out/update-documents-__vm_enough_memory-function-path.patch and later at http://ozlabs.org/~akpm/mmotm/broken-out/update-documents-__vm_enough_memory-function-path.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/process/submit-checklist.rst when testing your code *** The -mm tree is included into linux-next and is updated there every 3-4 working days ------------------------------------------------------ From: juviliu <juviliu@xxxxxxxxxxx> Subject: Documentation/sysctl/vm.txt: update __vm_enough_memory()'s path __vm_enough_memory has moved to mm/util.c. Link: http://lkml.kernel.org/r/E18EDF4A4FA4A04BBFA824B6D7699E532A7E5913@xxxxxxxxxxxxxxxxxxxxxxxxxxx Signed-off-by: Juvi Liu <juviliu@xxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- diff -puN Documentation/sysctl/vm.txt~update-documents-__vm_enough_memory-function-path Documentation/sysctl/vm.txt --- a/Documentation/sysctl/vm.txt~update-documents-__vm_enough_memory-function-path +++ a/Documentation/sysctl/vm.txt @@ -668,7 +668,7 @@ and don't use much of it. The default value is 0. See Documentation/vm/overcommit-accounting.rst and -mm/mmap.c::__vm_enough_memory() for more information. +mm/util.c::__vm_enough_memory() for more information. ============================================================== _ Patches currently in -mm which might be from juviliu@xxxxxxxxxxx are update-documents-__vm_enough_memory-function-path.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