The patch titled Subject: kmod.c: fix kernel-doc warning has been added to the -mm tree. Its filename is kmodc-fix-kernel-doc-warning.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: Randy Dunlap <rdunlap@xxxxxxxxxxxx> Subject: kmod.c: fix kernel-doc warning Warning(kernel/kmod.c:419): No description found for parameter 'depth' Signed-off-by: Randy Dunlap <rdunlap@xxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- kernel/kmod.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff -puN kernel/kmod.c~kmodc-fix-kernel-doc-warning kernel/kmod.c --- a/kernel/kmod.c~kmodc-fix-kernel-doc-warning +++ a/kernel/kmod.c @@ -409,7 +409,7 @@ EXPORT_SYMBOL_GPL(usermodehelper_read_un /** * __usermodehelper_set_disable_depth - Modify usermodehelper_disabled. - * depth: New value to assign to usermodehelper_disabled. + * @depth: New value to assign to usermodehelper_disabled. * * Change the value of usermodehelper_disabled (under umhelper_sem locked for * writing) and wakeup tasks waiting for it to change. _ Subject: Subject: kmod.c: fix kernel-doc warning Patches currently in -mm which might be from rdunlap@xxxxxxxxxxxx are origin.patch linux-next.patch fs-symlink-restrictions-on-sticky-directories.patch fs-hardlink-creation-restrictions.patch kmodc-fix-kernel-doc-warning.patch ramoops-use-pstore-interface.patch ramoops-use-pstore-interface-fix.patch kconfig-update-compression-algorithm-info.patch mutex-subsystem-synchro-test-module.patch mutex-subsystem-synchro-test-module-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