[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9f6c2d87-bb45-4c95-af93-7d2ca5f1dcc3@lunn.ch>
Date: Mon, 3 Feb 2025 14:29:23 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Simon Horman <horms@...nel.org>
Cc: Jakub Kicinski <kuba@...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, Feb 03, 2025 at 10:56:47AM +0000, Simon Horman wrote:
> On Sat, Feb 01, 2025 at 06:11:55PM -0800, Jakub Kicinski wrote:
> > I feel like we don't do a good enough keeping authors of driver
> > APIs around. The ethtool code base was very nicely compartmentalized
> > by Michal. Establish a precedent of creating MAINTAINERS entries
> > for "sections" of the ethtool API. Use Andrew and cable test as
> > a sample entry. The entry should ideally cover 3 elements:
> > a core file, test(s), and keywords. The last one is important
> > because we intend the entries to cover core code *and* reviews
> > of drivers implementing given API!
> >
> > Signed-off-by: Jakub Kicinski <kuba@...nel.org>
> > ---
> > 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?
>
> 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.
Even if it does explode, so what. Is ./scripts/get_maintainer.pl the
bottleneck in any workflows?
Andrew
Powered by blists - more mailing lists