Signed-off-by: Joe Perches <joe@perches.com>
---
 Documentation/SubmittingPatches |   17 +++++++++++++++++
 1 files changed, 17 insertions(+), 0 deletions(-)

diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index 689e237..bb318f9 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -176,6 +176,23 @@ discussed should the patch then be submitted to Linus.
 
 6) Select your CC (e-mail carbon copy) list.
 
+Use
+	"./scripts/get_maintainer.pl --nogit --roles <patch>"
+to find the appropriate maintainers and mailing lists to CC.
+
+If the output email addresses doesn't show a "supporter" or "maintainer",
+you can expand the search to include git history with:
+
+	"./scripts/get_maintainer.pl --roles <patch>"
+
+Searching git history can often list individuals that may not be
+particularly interested in your patch, so use the list of names
+judiciously.
+
+./scripts/get_maintainer.pl options "--rolestats" and "--git-blame"
+can show a bit more information and might help you select the appropriate
+parties to CC.
+
 Unless you have a reason NOT to do so, CC linux-kernel@vger.kernel.org.
 
 Other kernel developers besides Linus need to be aware of your change,