From: Geert Uytterhoeven <geert@linux-m68k.org>
To: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Cc: Vlastimil Babka <vbabka@suse.cz>, Joe Perches <joe@perches.com>,
Andrew Morton <akpm@linux-foundation.org>,
workflows@vger.kernel.org, "Theodore Ts'o" <tytso@mit.edu>,
"Bryan O'Donoghue" <bryan.odonoghue@linaro.org>,
Thorsten Leemhuis <linux@leemhuis.info>,
Kees Cook <kees@kernel.org>,
linux-kernel@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: [PATCH v2 1/2] get_maintainer: add --substatus for reporting subsystem status
Date: Tue, 11 Feb 2025 16:22:04 +0100 [thread overview]
Message-ID: <CAMuHMdVXgK3DiUjjOC==mm0SD8Fgtd44T+s2giPjD+G_c1tXeA@mail.gmail.com> (raw)
In-Reply-To: <wy6yhp2ty2s5wq76u7toghuuztdzb5f7uphfqkgw4t7vu4eojd@sc26ynxekxki>
Hi Uwe,
On Tue, 11 Feb 2025 at 16:09, Uwe Kleine-König
<u.kleine-koenig@baylibre.com> wrote:
> On Tue, Feb 11, 2025 at 11:48:13AM +0100, Geert Uytterhoeven wrote:
> > On Tue, 11 Feb 2025 at 11:32, Uwe Kleine-König
> > <u.kleine-koenig@baylibre.com> wrote:
> > > On Mon, Feb 03, 2025 at 12:13:16PM +0100, Vlastimil Babka wrote:
> > > > The subsystem status is currently reported with --role(stats) by
> > > > adjusting the maintainer role for any status different from Maintained.
> > > > This has two downsides:
> > > >
> > > > - if a subsystem has only reviewers or mailing lists and no maintainers,
> > > > the status is not reported (i.e. typically, Orphan subsystems have no
> > > > maintainers)
> > > >
> > > > - the Supported status means that someone is paid for maintaining, but
> > > > it is reported as "supporter" for all the maintainers, which can be
> > > > incorrect. People have been also confused about what "supporter"
> > > > means.
> > > >
> > > > This patch introduces a new --substatus option and functionality aimed
> > > > to report the subsystem status separately, without adjusting the
> > > > reported maintainer role. After the e-mails are output, the status of
> > > > subsystems will follow, for example:
> > > >
> > > > ...
> > > > linux-kernel@vger.kernel.org (open list:LIBRARY CODE)
> > > > LIBRARY CODE status: Supported
> > > >
> > > > In order to allow replacing the role rewriting seamlessly, the new
> > > > option works as follows:
> > > >
> > > > - it is automatically enabled when --email and --role are enabled
> > > > (the defaults include --email and --rolestats which implies --role)
> > > >
> > > > - usages with --norolestats e.g. for git's --cc-cmd will thus need no
> > > > adjustments
> > > >
> > > > - the most common Maintained status is not reported at all, to reduce
> > > > unnecessary noise
> > > >
> > > > - THE REST catch-all section (contains lkml) status is not reported
> > > >
> > > > - the existing --subsystem and --status options are unaffected so their
> > > > users will need no adjustments
> > > >
> > > > Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
> > >
> > > This patch is in next as c1565b6f7b53ea1ea3e757538832e12d7d13d949. It
> > > breaks one of my scripts that I use to semi-automatically determine
> > > recipents for patch series.
> > >
> > > It works as follows:
> > >
> > > $ batch-add-recipents audin-patch-v1/0001-ASoC-meson-HACK-let-AIU-export-its-clocks-through-cl.patch
> > > #!/bin/sh
> > >
> > > addrecipent \
> > > -t "Rob Herring <robh@kernel.org>" $(: maintainer:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS) \
> > > -t "Krzysztof Kozlowski <krzk+dt@kernel.org>" $(: maintainer:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS) \
> > > -t "Conor Dooley <conor+dt@kernel.org>" $(: maintainer:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS) \
> > > -t "Neil Armstrong <neil.armstrong@linaro.org>" $(: maintainer:ARM/Amlogic Meson SoC support) \
> > > -t "Kevin Hilman <khilman@baylibre.com>" $(: maintainer:ARM/Amlogic Meson SoC support) \
> > > -c "Jerome Brunet <jbrunet@baylibre.com>" $(: reviewer:ARM/Amlogic Meson SoC support) \
> > > -c "Martin Blumenstingl <martin.blumenstingl@googlemail.com>" $(: reviewer:ARM/Amlogic Meson SoC support) \
> > > -t "Liam Girdwood <lgirdwood@gmail.com>" $(: supporter:SOUND - SOC LAYER / DYNAMIC AUDIO POWER MANAGEM...) \
> > > -t "Mark Brown <broonie@kernel.org>" $(: supporter:SOUND - SOC LAYER / DYNAMIC AUDIO POWER MANAGEM...) \
> > > -t "Jaroslav Kysela <perex@perex.cz>" $(: maintainer:SOUND) \
> > > -t "Takashi Iwai <tiwai@suse.com>" $(: maintainer:SOUND) \
> > > -c "devicetree@vger.kernel.org" $(: open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS) \
> > > -c "linux-arm-kernel@lists.infradead.org" $(: moderated list:ARM/Amlogic Meson SoC support) \
> > > -c "linux-amlogic@lists.infradead.org" $(: open list:ARM/Amlogic Meson SoC support) \
> > > -c "linux-kernel@vger.kernel.org" $(: open list) \
> > > -c "linux-sound@vger.kernel.org" $(: open list:SOUND - SOC LAYER / DYNAMIC AUDIO POWER MANAGEM...) \
> > > audin-patch-v1/0001-ASoC-meson-HACK-let-AIU-export-its-clocks-through-cl.patch
> >
> > Hey, that looks familiar ;-)
> >
> > > the output is usually redirected to a file that I edit before running
> > > it. The additional line in the output of
> > >
> > > scripts/get_maintainer.pl audin-patch-v1/0001-ASoC-meson-HACK-let-AIU-export-its-clocks-through-cl.patch
> > >
> > > with your change breaks that script.
> >
> > You forgot to list the additional output?
> >
> > I gave it a try with my script, and with one of my own patches.
> > Example additional output is:
> >
> > --cc "ARM/Microchip" $(: AT91] SoC support status: Supported \
> > --cc "QAT DRIVER status: Supported \
> > --cc "ARM/ASPEED MACHINE SUPPORT status: Supported \
> > --cc "MELEXIS MLX90614 DRIVER status: Supported \
> > --cc "ARM/NUVOTON MA35 ARCHITECTURE status: Supported \
> > --cc "ARM/RISC-V/RENESAS ARCHITECTURE status: Supported \
>
> Is that really your output? No closing ) in the first line and no
> closing " in the 5 last?
Yes it is....
As I need to delete the lines anyway, invalid syntax is irrelevant ;-)
> For me it's worse(?), I get:
>
> $ batch-add-recipents audin-patch-v1/0001-ASoC-meson-HACK-let-AIU-export-its-clocks-through-cl.patch
> #!/bin/sh
>
> addrecipent \
> -t "Rob Herring <robh@kernel.org>" $(: maintainer:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS) \
> -t "Krzysztof Kozlowski <krzk+dt@kernel.org>" $(: maintainer:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS) \
> -t "Conor Dooley <conor+dt@kernel.org>" $(: maintainer:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS) \
> -t "Neil Armstrong <neil.armstrong@linaro.org>" $(: maintainer:ARM/Amlogic Meson SoC support) \
> -t "Kevin Hilman <khilman@baylibre.com>" $(: maintainer:ARM/Amlogic Meson SoC support) \
> -c "Jerome Brunet <jbrunet@baylibre.com>" $(: reviewer:ARM/Amlogic Meson SoC support) \
> -c "Martin Blumenstingl <martin.blumenstingl@googlemail.com>" $(: reviewer:ARM/Amlogic Meson SoC support) \
> -t "Liam Girdwood <lgirdwood@gmail.com>" $(: maintainer:SOUND - SOC LAYER / DYNAMIC AUDIO POWER MANAGEM...) \
> -t "Mark Brown <broonie@kernel.org>" $(: maintainer:SOUND - SOC LAYER / DYNAMIC AUDIO POWER MANAGEM...) \
> -t "Jaroslav Kysela <perex@perex.cz>" $(: maintainer:SOUND) \
> -t "Takashi Iwai <tiwai@suse.com>" $(: maintainer:SOUND) \
> -c "devicetree@vger.kernel.org" $(: open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS) \
> -c "linux-arm-kernel@lists.infradead.org" $(: moderated list:ARM/Amlogic Meson SoC support) \
> -c "linux-amlogic@lists.infradead.org" $(: open list:ARM/Amlogic Meson SoC support) \
> -c "linux-kernel@vger.kernel.org" $(: open list) \
> -c "linux-sound@vger.kernel.org" $(: open list:SOUND - SOC LAYER / DYNAMIC AUDIO POWER MANAGEM...) \
> Failed to parse "SOUND - SOC LAYER / DYNAMIC AUDIO POWER MANAGEMENT (ASoC) status: Supported
> " at -e line 6, <> line 17.
Oops...
My version is also not perfect. I'm used to doing manual adjustments...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2025-02-11 15:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 11:13 [PATCH v2 0/2] get_maintainer: report subsystem status separately from maintainer role Vlastimil Babka
2025-02-03 11:13 ` [PATCH v2 1/2] get_maintainer: add --substatus for reporting subsystem status Vlastimil Babka
2025-02-04 10:19 ` Lorenzo Stoakes
2025-02-11 10:32 ` Uwe Kleine-König
2025-02-11 10:48 ` Geert Uytterhoeven
2025-02-11 10:59 ` Vlastimil Babka
2025-02-11 11:05 ` Vlastimil Babka
2025-02-11 15:19 ` Geert Uytterhoeven
2025-02-11 15:30 ` Vlastimil Babka
2025-02-11 16:28 ` Geert Uytterhoeven
2025-02-11 18:39 ` Vlastimil Babka
2025-02-11 15:09 ` Uwe Kleine-König
2025-02-11 15:22 ` Geert Uytterhoeven [this message]
2025-02-11 15:20 ` Vlastimil Babka
2025-02-12 12:42 ` Geert Uytterhoeven
2025-02-12 14:53 ` Uwe Kleine-König
2025-02-03 11:13 ` [PATCH v2 2/2] get_maintainer: stop reporting subsystem status as maintainer role Vlastimil Babka
2025-02-04 10:18 ` Lorenzo Stoakes
2025-02-04 10:12 ` [PATCH v2 0/2] get_maintainer: report subsystem status separately from " Lorenzo Stoakes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMuHMdVXgK3DiUjjOC==mm0SD8Fgtd44T+s2giPjD+G_c1tXeA@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=akpm@linux-foundation.org \
--cc=bryan.odonoghue@linaro.org \
--cc=joe@perches.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=tytso@mit.edu \
--cc=u.kleine-koenig@baylibre.com \
--cc=vbabka@suse.cz \
--cc=workflows@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox