Documentation/SubmittingPatches: suggested the use of scripts/get_maintainer.pl

Had I found a reference to scripts/get_maintainer.pl when I first read
Documentation/SubmittingPatches, it would've saved me some time.

Signed-off-by: Michel Machado <[email protected]>
Acked-by: Rob Landley <[email protected]>
Signed-off-by: Jiri Kosina <[email protected]>

diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index 4468ce24427cb011e7991d8f1ae2560764b170b8..c379a2a6949f1c1cac04fb6f185c633512f37061 100644 (file)
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -150,7 +150,8 @@ be able to justify all violations that remain in your patch.
 
 Look through the MAINTAINERS file and the source code, and determine
 if your change applies to a specific subsystem of the kernel, with
-an assigned maintainer.  If so, e-mail that person.
+an assigned maintainer.  If so, e-mail that person.  The script
+scripts/get_maintainer.pl can be very useful at this step.
 
 If no maintainer is listed, or the maintainer does not respond, send
 your patch to the primary Linux kernel developer's mailing list,