On 28/09/2022 02:30, Bryan O'Donoghue wrote: > Recently when submitting a yaml change I found that I had omitted the > maintainer whose tree the change needed to go through. Thank you for your patch. There is something to discuss/improve. > diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst > index be49d8f2601b4..5f97379da41da 100644 > --- a/Documentation/process/submitting-patches.rst > +++ b/Documentation/process/submitting-patches.rst > @@ -227,9 +227,11 @@ You should always copy the appropriate subsystem maintainer(s) on any patch > to code that they maintain; look through the MAINTAINERS file and the > source code revision history to see who those maintainers are. The > script scripts/get_maintainer.pl can be very useful at this step (pass paths to > -your patches as arguments to scripts/get_maintainer.pl). If you cannot find a > -maintainer for the subsystem you are working on, Andrew Morton > -(akpm@xxxxxxxxxxxxxxxxxxxx) serves as a maintainer of last resort. > +your patches as arguments to scripts/get_maintainer.pl). You should mail > +everyone who appears as "maintainer" or "supporter" in the > +scripts/get_maintainer.pl output. If you cannot find a maintainer for the > +subsystem you are working on, Andrew Morton (akpm@xxxxxxxxxxxxxxxxxxxx) serves > +as a maintainer of last resort. That's still a bit misleading, because you should also send the patch to reviewers and mailing lists. :) Best regards, Krzysztof
