netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Jan Petrous <jan.petrous@oss.nxp.com>,
	NXP S32 Linux Team <s32@nxp.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: fix DWMAC S32 entry
Date: Fri, 21 Feb 2025 00:22:12 +0000	[thread overview]
Message-ID: <Z7fHNEFo7Aa4jfUO@shell.armlinux.org.uk> (raw)
In-Reply-To: <20250220152248.3c05878a@kernel.org>

On Thu, Feb 20, 2025 at 03:22:48PM -0800, Jakub Kicinski wrote:
> On Tue, 18 Feb 2025 09:23:14 +0000 Russell King (Oracle) wrote:
> > Using L: with more than a bare email address causes getmaintainer.pl
> > to be unable to parse the entry. Fix this by doing as other entries
> > that use this email address and convert it to an R: entry.
> > 
> > Signed-off-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
> > ---
> >  MAINTAINERS | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index de81a3d68396..7da5d2df1b45 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -2877,7 +2877,7 @@ F:	drivers/pinctrl/nxp/
> >  
> >  ARM/NXP S32G/S32R DWMAC ETHERNET DRIVER
> >  M:	Jan Petrous <jan.petrous@oss.nxp.com>
> > -L:	NXP S32 Linux Team <s32@nxp.com>
> > +R:	NXP S32 Linux Team <s32@nxp.com>
> >  S:	Maintained
> 
> I had to look thru old commits, 8b0f64b113d61 specifically.
> Can we also strip the "NXP S32 Linux Team"
> It's pretty obvious from s32@nxp.com that it's a group address,
> and this way our scripts will know that this is not a real reviewer.

Right now, the situation is:

$ grep s32@nxp.com MAINTAINERS
R:      NXP S32 Linux Team <s32@nxp.com>
L:      NXP S32 Linux Team <s32@nxp.com>
R:      NXP S32 Linux Team <s32@nxp.com>
L:      s32@nxp.com

and the approach that has been taken in the past is:

-L:     NXP S32 Linux Team <s32@nxp.com>
+R:     NXP S32 Linux Team <s32@nxp.com>

in commit bb2de9b04942 ("MAINTAINERS: fix list entries with display names")

However, commit 98dcb872779f ("ARM: s32c: update MAINTAINERS entry") did
the reverse for the "ARM/NXP S32G ARCHITECTURE" entry breaking that and
adding a new instance of this breakage elsewhere.

It seems these are just going to flip back and forth, so I don't think
I can be bothered to try to fix it, and will modify my own scripts to
eliminate the blank entry in get_maintainers output because of this.
(In other words, s32@nxp.com will *not* be Cc'd for any patches I send.)


-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!

  reply	other threads:[~2025-02-21  0:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-18  9:23 [PATCH] MAINTAINERS: fix DWMAC S32 entry Russell King (Oracle)
2025-02-18 15:58 ` Andrew Lunn
2025-02-20 23:22 ` Jakub Kicinski
2025-02-21  0:22   ` Russell King (Oracle) [this message]
2025-02-21  0:48     ` Jakub Kicinski
2025-02-21  8:43       ` Russell King (Oracle)

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=Z7fHNEFo7Aa4jfUO@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=jan.petrous@oss.nxp.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=s32@nxp.com \
    /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;
as well as URLs for NNTP newsgroup(s).