netdev - Re: [PATCH net 2/2] MAINTAINERS: add a sample ethtool section 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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <8ef9275a-b5f9-45e2-a99c-096fb3213ed8@redhat.com>
Date: Tue, 4 Feb 2025 10:26:40 +0100
From: Paolo Abeni <pabeni@...hat.com>
To: Jakub Kicinski <kuba@...nel.org>, davem@...emloft.net
Cc: netdev@...r.kernel.org, edumazet@...gle.com, andrew+netdev@...n.ch,
 horms@...nel.org
Subject: Re: [PATCH net 2/2] MAINTAINERS: add a sample ethtool section entry

On 2/2/25 3:11 AM, Jakub Kicinski wrote:
> This patch is a nop from process perspective, since Andrew already
> is a maintainer and reviews all this code. Let's focus on discussing
> merits of the "section entries" in abstract?

Should the keyword be a little more generic, i.e. just 'cable_test'?
AFAICS the current one doesn't catch the device drivers,

I agree encouraging more driver API reviewer would be great, but I
personally have a slight preference to add/maintain entries only they
actually affect the process.

What about tying the creation of the entry to some specific contribution?

/P