From: Andrew Lunn <andrew@lunn.ch>
To: Wenzhao Liao <wenzhaoliao@ruc.edu.cn>
Cc: rust-for-linux@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, ojeda@kernel.org, boqun@kernel.org,
gary@garyguo.net, bjorn3_gh@protonmail.com, lossin@kernel.org,
a.hindborg@kernel.org, aliceryhl@google.com, tmgross@umich.edu,
dakr@kernel.org, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com
Subject: Re: [RFC PATCH 0/6] rust: net: introduce minimal rtnl/netdevice abstractions and nlmon reference driver
Date: Thu, 2 Apr 2026 22:00:28 +0200 [thread overview]
Message-ID: <bd785bda-fd5d-4bfe-9e75-acebd6d7184a@lunn.ch> (raw)
In-Reply-To: <20260402163640.1079056-1-wenzhaoliao@ruc.edu.cn>
On Thu, Apr 02, 2026 at 12:36:34PM -0400, Wenzhao Liao wrote:
> Hi,
>
> This RFC proposes a minimal set of Rust networking abstractions for
> link-type drivers, together with a Rust implementation of nlmon as a
> reference driver.
nlmon exists. Why would we want a second implementation in Rust?
It seems like we keep getting Rust submissions for the sake of
submitting Rust. We never seem to get Rust code adding something new,
something which does not already exist.
Please, if you want to submit Rust code, find a device which does not
have a driver and write a driver for it, in Rust. Or find a protocol
described in an RFC which we don't implement, and write a Rust
implementation. Or find a new firewall rule which cannot be described
using the current code, and implement it in Rust.
Unless it is something new, i doubt it will get accepted.
Andrew
next prev parent reply other threads:[~2026-04-02 20:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 16:36 [RFC PATCH 0/6] rust: net: introduce minimal rtnl/netdevice abstractions and nlmon reference driver Wenzhao Liao
2026-04-02 16:36 ` [RFC PATCH 1/6] rust: bindings: expose networking headers needed by nlmon Wenzhao Liao
2026-04-02 16:36 ` [RFC PATCH 2/6] rust: helpers: add net_device and sk_buff helper wrappers Wenzhao Liao
2026-04-02 16:36 ` [RFC PATCH 3/6] rust: net: add minimal skbuff, netdevice, and stats abstractions Wenzhao Liao
2026-04-02 16:36 ` [RFC PATCH 4/6] rust: net: add minimal rtnl registration and netlink tap support Wenzhao Liao
2026-04-02 16:36 ` [RFC PATCH 5/6] net: add Rust reference driver for nlmon Wenzhao Liao
2026-04-02 16:36 ` [RFC PATCH 6/6] MAINTAINERS: add Rust net and nlmon entries Wenzhao Liao
2026-04-02 20:00 ` Andrew Lunn [this message]
[not found] ` <APYAlQCNKK5EzEq6n4bgjqou.3.1775205609812.Hmail.2023000929@ruc.edu.cn>
2026-04-03 14:56 ` Re: [RFC PATCH 0/6] rust: net: introduce minimal rtnl/netdevice abstractions and nlmon reference driver Andrew Lunn
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=bd785bda-fd5d-4bfe-9e75-acebd6d7184a@lunn.ch \
--to=andrew@lunn.ch \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=andrew+netdev@lunn.ch \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gary@garyguo.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=pabeni@redhat.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=wenzhaoliao@ruc.edu.cn \
/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