The patch titled Documentation: sysctl/kernel.txt: fix documentation reference has been added to the -mm tree. Its filename is documentation-sysctl-kerneltxt-fix-documentation-reference.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 *** See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find out what to do about this The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ ------------------------------------------------------ Subject: Documentation: sysctl/kernel.txt: fix documentation reference From: Michael Opdenacker <michael-lists@xxxxxxxxxxxxxxxxxx> This patch fixes a reference to Documentation/kmod.txt which was apparently renamed to Documentation/debugging-modules.txt Signed-off-by: Michael Opdenacker <michael@xxxxxxxxxxxxxxxxxx> Cc: "Randy.Dunlap" <rdunlap@xxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- Documentation/sysctl/kernel.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff -puN Documentation/sysctl/kernel.txt~documentation-sysctl-kerneltxt-fix-documentation-reference Documentation/sysctl/kernel.txt --- a/Documentation/sysctl/kernel.txt~documentation-sysctl-kerneltxt-fix-documentation-reference +++ a/Documentation/sysctl/kernel.txt @@ -29,7 +29,7 @@ show up in /proc/sys/kernel: - java-interpreter [ binfmt_java, obsolete ] - kstack_depth_to_print [ X86 only ] - l2cr [ PPC only ] -- modprobe ==> Documentation/kmod.txt +- modprobe ==> Documentation/debugging-modules.txt - msgmax - msgmnb - msgmni _ Patches currently in -mm which might be from michael-lists@xxxxxxxxxxxxxxxxxx are origin.patch documentation-sysctl-kerneltxt-fix-documentation-reference.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