[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72kS=--E_v9no=pFtxArxtxWNrAbgcAa4LUz28CYozbVWg@mail.gmail.com>
Date: Fri, 13 Oct 2023 20:43:21 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Trevor Gross <tmgross@...ch.edu>
Cc: Boqun Feng <boqun.feng@...il.com>, FUJITA Tomonori <fujita.tomonori@...il.com>,
netdev@...r.kernel.org, rust-for-linux@...r.kernel.org, andrew@...n.ch,
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 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.
Cheers,
Miguel
Powered by blists - more mailing lists