linux-kernel - Re: [PATCH] MAINTAINERS: fix DWMAC S32 entry

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <Z7g8vk-MrDQ271Dz@shell.armlinux.org.uk>
Date: Fri, 21 Feb 2025 08:43:42 +0000
From: "Russell King (Oracle)" <linux@...linux.org.uk>
To: Jakub Kicinski <kuba@...nel.org>
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 Thu, Feb 20, 2025 at 04:48:19PM -0800, Jakub Kicinski wrote:
> 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 :/

My point is that "fixing" it will only get unfixed later - as can be
seen from the history of the s32 entries already present. They flip-flop
between R: and L: as people's ideas about what is correct change.

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