[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250220164819.044b509f@kernel.org>
Date: Thu, 20 Feb 2025 16:48:19 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: "Russell King (Oracle)" <linux@...linux.org.uk>
Cc: Jan Petrous <jan.petrous@....nxp.com>, NXP S32 Linux Team <s32@....com>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] MAINTAINERS: fix DWMAC S32 entry
On Fri, 21 Feb 2025 00:22:12 +0000 Russell King (Oracle) wrote:
> Right now, the situation is:
>
> $ grep s32@....com MAINTAINERS
> R: NXP S32 Linux Team <s32@....com>
> L: NXP S32 Linux Team <s32@....com>
> R: NXP S32 Linux Team <s32@....com>
> L: s32@....com
>
> and the approach that has been taken in the past is:
>
> -L: NXP S32 Linux Team <s32@....com>
> +R: NXP S32 Linux Team <s32@....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@....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 :/
Powered by blists - more mailing lists