path: root/Documentation/SubmittingPatches
diff options
authorMichel Machado <>2012-04-02 22:10:53 -0400
committerJiri Kosina <>2012-05-25 16:18:30 +0200
commite52d2e1f25f03edf7628fae219150d8dc5023081 (patch)
treec1594e04583cd79518c48955ceedc85ac1ceba67 /Documentation/SubmittingPatches
parent9b170dbd82448826ca3b8b6ee47daf36c4f438f3 (diff)
Documentation/SubmittingPatches: suggested the use of scripts/
Had I found a reference to scripts/ when I first read Documentation/SubmittingPatches, it would've saved me some time. Signed-off-by: Michel Machado <> Acked-by: Rob Landley <> Signed-off-by: Jiri Kosina <>
Diffstat (limited to 'Documentation/SubmittingPatches')
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/ 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,