[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f74a9883-3a9b-8606-b20d-f046835fb827@linaro.org>
Date: Wed, 28 Sep 2022 08:53:06 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Bryan O'Donoghue <bryan.odonoghue@...aro.org>, corbet@....net,
linux@...mhuis.info, konstantin@...uxfoundation.org,
linux-doc@...r.kernel.org
Cc: linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Documentation/process: Add text to indicate supporters
should be mailed
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@...ux-foundation.org) 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@...ux-foundation.org) 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
Powered by blists - more mailing lists