All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: "Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>
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: Thu, 20 Feb 2025 15:22:48 -0800	[thread overview]
Message-ID: <20250220152248.3c05878a@kernel.org> (raw)
In-Reply-To: <E1tkJow-004Nfn-Cs@rmk-PC.armlinux.org.uk>

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.
-- 
pw-bot: cr

  parent reply	other threads:[~2025-02-20 23: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 [this message]
2025-02-21  0:22   ` Russell King (Oracle)
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=20250220152248.3c05878a@kernel.org \
    --to=kuba@kernel.org \
    --cc=jan.petrous@oss.nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rmk+kernel@armlinux.org.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.