|author||Michel Machado <email@example.com>||2012-04-02 22:10:53 -0400|
|committer||Jiri Kosina <firstname.lastname@example.org>||2012-05-25 16:18:30 +0200|
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@example.com> Acked-by: Rob Landley <firstname.lastname@example.org> Signed-off-by: Jiri Kosina <email@example.com>
Diffstat (limited to 'Documentation/SubmittingPatches')
1 files changed, 2 insertions, 1 deletions
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index 4468ce24427..c379a2a6949 100644
@@ -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,