[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0948fa3f-2421-47ad-89fc-8b0992d9f021@lunn.ch>
Date: Fri, 13 Oct 2023 20:49:29 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
Cc: Trevor Gross <tmgross@...ch.edu>, Boqun Feng <boqun.feng@...il.com>,
FUJITA Tomonori <fujita.tomonori@...il.com>, netdev@...r.kernel.org,
rust-for-linux@...r.kernel.org, wedsonaf@...il.com,
benno.lossin@...ton.me, greg@...ah.com
Subject: Re: [PATCH net-next v4 3/4] MAINTAINERS: add Rust PHY abstractions
to the ETHERNET PHY LIBRARY
On Fri, Oct 13, 2023 at 08:43:21PM +0200, Miguel Ojeda wrote:
> On Fri, Oct 13, 2023 at 6:17 PM Trevor Gross <tmgross@...ch.edu> wrote:
> >
> > Thanks for the suggestion Boqun :) I would be happy to be a reviewer
> > for the rust components of networking.
>
> Thanks a lot Trevor!
>
> > As Tomo mentioned I am not sure there is a good way to indicate this
> > niche, maybe a new section with two lists? Andrew's call for what
> > would be best here I suppose.
>
> Yes, maintainers may prefer to split it or not (e.g. "ETHERNET PHY
> LIBRARY [RUST]"). Then Tomo and you can be there.
>
> That also allows to list only the relevant files in `F:`, to have an
> extra `L:` for rust-for-linux (in the beginning), a different `S:`
> level if needed, etc.
Yes, this seems sensible.
I would also suggest a new entry for the driver.
Play with ./script/get_maintainer.pl --file and make sure it picks the
right people for a particular file.
Andrew
Powered by blists - more mailing lists