From: Jakub Kicinski <kuba@kernel.org>
To: "Russell King (Oracle)" <linux@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 16:48:19 -0800 [thread overview]
Message-ID: <20250220164819.044b509f@kernel.org> (raw)
In-Reply-To: <Z7fHNEFo7Aa4jfUO@shell.armlinux.org.uk>
On Fri, 21 Feb 2025 00:22:12 +0000 Russell King (Oracle) wrote:
> 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.)
Literally would have taken you less time to fix it how I asked than
type this email :/
next prev parent reply other threads:[~2025-02-21 0:48 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)
2025-02-21 0:48 ` Jakub Kicinski [this message]
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=20250220164819.044b509f@kernel.org \
--to=kuba@kernel.org \
--cc=jan.petrous@oss.nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--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).