summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMichel Machado <michel@digirati.com.br>2012-04-02 22:10:53 -0400
committerJiri Kosina <jkosina@suse.cz>2012-05-25 16:18:30 +0200
commite52d2e1f25f03edf7628fae219150d8dc5023081 (patch)
treec1594e04583cd79518c48955ceedc85ac1ceba67
parent9b170dbd82448826ca3b8b6ee47daf36c4f438f3 (diff)
downloadtalos-op-linux-e52d2e1f25f03edf7628fae219150d8dc5023081.tar.gz
talos-op-linux-e52d2e1f25f03edf7628fae219150d8dc5023081.zip
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 <michel@digirati.com.br> Acked-by: Rob Landley <rob@landley.net> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
-rw-r--r--Documentation/SubmittingPatches3
1 files changed, 2 insertions, 1 deletions
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index 4468ce24427c..c379a2a6949f 100644
--- 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,
OpenPOWER on IntegriCloud