From: Alice Ryhl <aliceryhl@google.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "Donald Hunter" <donald.hunter@gmail.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Andrew Lunn" <andrew@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
"Carlos Llamas" <cmllamas@google.com>,
"Eric Dumazet" <edumazet@google.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"Simon Horman" <horms@kernel.org>,
"Matthew Maurer" <mmaurer@google.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun@kernel.org>, "Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Christian Brauner" <brauner@kernel.org>,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH v5 1/2] rust: netlink: add raw netlink abstraction
Date: Thu, 28 May 2026 06:25:48 +0000 [thread overview]
Message-ID: <ahff7OTzS46Rti5c@google.com> (raw)
In-Reply-To: <20260527192130.21dabf08@kernel.org>
On Wed, May 27, 2026 at 07:21:30PM -0700, Jakub Kicinski wrote:
> On Wed, 27 May 2026 10:00:40 +0000 Alice Ryhl wrote:
> > On Tue, May 26, 2026 at 04:29:26PM +0200, Miguel Ojeda wrote:
> > > On Mon, May 25, 2026 at 3:17 PM Alice Ryhl <aliceryhl@google.com> wrote:
> > > >
> > > > This implements a safe and relatively simple API over the netlink API,
> > > > that allows you to add different attributes to a netlink message and
> > > > broadcast it. As the first user of this API only makes use of broadcast,
> > > > only broadcast messages are supported here.
> > >
> > > > rust/kernel/netlink.rs | 336 ++++++++++++++++++++++++++++++++++++++++
> > >
> > > This should be added to an existing or new `MAINTAINERS` entry, i.e.
> > > as usual, either inheriting it if the maintainers want, or delegating
> > > it to a sub- or co-maintainer, etc. depending on what people want.
>
> Good call, missed this isn't under rust/kernel/net
>
> > Netdev maintainers, what do you prefer that I put for these files? I'm
> > of course happy to be on the hook for this code.
>
> Can we put it under rust/kernel/net and rust/helpers/net ?
> And then add those directories to networking ?
> Just so that we don't have to keep wondering with every little piece
> of code.
Sure, will do.
However, it doesn't look like rust/kernel/net/ is listed under any
MAINTAINERS entry either.
> > Of course, it would be useful to have others listed here, as I'm sure I
> > will have questions about how networking works if there are patches in
> > this area. Or perhaps the netdev@ list itself is enough for that to
> > reach the right people?
> >
> > With regards to actually merging code in this area, then I think for
> > this particular series it is simpler to let Greg take it through
> > char-misc with all the other Binder changes. But for any future changes
> > to netlink.rs, I think it makes sense for them to land through the
> > netdev tree.
>
> SG, once acked it can go via any tree. Greg's tree make sense.
SG, thanks!
Alice
next prev parent reply other threads:[~2026-05-28 6:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 13:17 [PATCH v5 0/2] Rust netlink support + use in Rust Binder Alice Ryhl
2026-05-25 13:17 ` [PATCH v5 1/2] rust: netlink: add raw netlink abstraction Alice Ryhl
2026-05-26 14:29 ` Miguel Ojeda
2026-05-27 10:00 ` Alice Ryhl
2026-05-28 2:21 ` Jakub Kicinski
2026-05-28 6:25 ` Alice Ryhl [this message]
2026-05-25 13:17 ` [PATCH v5 2/2] rust_binder: report netlink transactions Alice Ryhl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ahff7OTzS46Rti5c@google.com \
--to=aliceryhl@google.com \
--cc=a.hindborg@kernel.org \
--cc=andrew@lunn.ch \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=brauner@kernel.org \
--cc=cmllamas@google.com \
--cc=dakr@kernel.org \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=mmaurer@google.com \
--cc=netdev@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=pabeni@redhat.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox