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: <20250203084627.54982995@kernel.org>
Date: Mon, 3 Feb 2025 08:46:27 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Andrew Lunn <andrew@...n.ch>
Cc: Simon Horman <horms@...nel.org>, davem@...emloft.net,
 netdev@...r.kernel.org, edumazet@...gle.com, pabeni@...hat.com,
 andrew+netdev@...n.ch
Subject: Re: [PATCH net 2/2] MAINTAINERS: add a sample ethtool section entry

On Mon, 3 Feb 2025 14:29:23 +0100 Andrew Lunn wrote:
> > In the first instance this seems like a good direction to go in to me.
> > My only slight concern is that we might see an explosion in entries.  
> 
> I don't think that will happen. I don't think we really have many
> sections of ethtool which people personally care about, always try to
> review across all drivers.

Agreed, FWIW.

> Even if it does explode, so what. Is ./scripts/get_maintainer.pl the
> bottleneck in any workflows?

Only concern there could be the keywords, we had issues with regexps
being too expensive in the past. There are plenty examples of how to
do them right now, tho.