linux-kernel - Re: [RESEND PATCH] MAINTAINERS: Fix list entries with display names

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAL_JsqKEfMOhwBogo6H657+AW_FVzv7Pacm5ZeYN1jg8v2svqA@mail.gmail.com>
Date: Fri, 3 Jan 2025 08:08:16 -0600
From: Rob Herring <robh@...nel.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Joe Perches <joe@...ches.com>, Arnd Bergmann <arnd@...db.de>, linux-kernel@...r.kernel.org
Subject: Re: [RESEND PATCH] MAINTAINERS: Fix list entries with display names

On Thu, Jan 2, 2025 at 5:47 PM Andrew Morton <akpm@...ux-foundation.org> wrote:
>
> On Tue, 31 Dec 2024 09:54:14 -0600 "Rob Herring (Arm)" <robh@...nel.org> wrote:
>
> > get_maintainers.pl doesn't expect list entries to have a display name.
> > Entries with a display name are omitted and print just the description:
> >
> >  (open list:PIN CONTROLLER - FREESCALE)
> >
> > These cases are pretty much aliases to a few people, not lists which
> > are archived and can be subscribed to. Change these cases to be reviewers
> > instead.
>
> Feels a bit wrong.  Are you sure that *all* of the below "lists" are
> not really lists?  If so then OK I suppose.  Or perhaps we should have
> a new MAINTAINERS tag to cover this situation.

They certainly don't look like anything anyone outside those
organizations can subscribe to or would have public archives. Whether
they are lists or aliases internally doesn't matter to us.

> And shouldn't get_maintainer be made to be more friendly in its
> handling of these entries?  Omitting the email address seems kinda dumb.

That's certainly an alternate or additional fix. I was hoping Joe
would know where to fix that rather than me trying to wade thru perl.
:)

Rob