From: Joe Perches <joe@perches.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: linux-kernel@vger.kernel.org, kernel@pengutronix.de
Subject: Re: get_maintainer broken for a few entries in MAINTAINERS
Date: Mon, 08 May 2023 01:13:30 -0700 [thread overview]
Message-ID: <1a559a83d3519a849eb93ade955d90c1c19af884.camel@perches.com> (raw)
In-Reply-To: <20230508074731.jlzuvx6yr336xmvp@pengutronix.de>
On Mon, 2023-05-08 at 09:47 +0200, Uwe Kleine-König wrote:
> Hello,
>
> on v6.3 and v6.4-rc1 I experience:
>
> $ scripts/get_maintainer.pl -f drivers/gpu/drm/arm/display/komeda
> "James (Qian) Wang" <james.qian.wang@arm.com> (supporter:ARM KOMEDA DRM-KMS DRIVER)
> Liviu Dudau <liviu.dudau@arm.com> (supporter:ARM KOMEDA DRM-KMS DRIVER)
> Mihail Atanassov <mihail.atanassov@arm.com> (supporter:ARM KOMEDA DRM-KMS DRIVER)
> Brian Starkey <brian.starkey@arm.com> (supporter:ARM MALI-DP DRM DRIVER)
> David Airlie <airlied@gmail.com> (maintainer:DRM DRIVERS)
> Daniel Vetter <daniel@ffwll.ch> (maintainer:DRM DRIVERS)
> (open list:ARM KOMEDA DRM-KMS DRIVER)
> dri-devel@lists.freedesktop.org (open list:DRM DRIVERS)
> linux-kernel@vger.kernel.org (open list)
>
> The 7th entry is broken. I didn't try to debug that in the script. Doing
>
> -L: Mali DP Maintainers <malidp@foss.arm.com>
> +L: malidp@foss.arm.com
>
> (twice) in MAINTAINTERS fixes the output.
More like the entries in MAINTAINERS are broken.
L: entries should not have "names".
I suggest sending a patch to MAINTAINERS to remove the "names"
or change the non-conforming entries to "M:"
$ git grep -h "^L:" MAINTAINERS | \
grep -v -P "^L:\s+[\w\_\.-]+@[\w_-]+\.\w+"
L: Mali DP Maintainers <malidp@foss.arm.com>
L: Mali DP Maintainers <malidp@foss.arm.com>
L: The AWS Nitro Enclaves Team <aws-nitro-enclaves-devel@amazon.com>
prev parent reply other threads:[~2023-05-08 8:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 7:47 Uwe Kleine-König
2023-05-08 8:13 ` Joe Perches [this message]
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=1a559a83d3519a849eb93ade955d90c1c19af884.camel@perches.com \
--to=joe@perches.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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
all inboxes | Powered by JetHome®