[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230614230128.199724bd@kernel.org>
Date: Wed, 14 Jun 2023 23:01:28 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: FUJITA Tomonori <fujita.tomonori@...il.com>
Cc: netdev@...r.kernel.org, rust-for-linux@...r.kernel.org,
aliceryhl@...gle.com, andrew@...n.ch, miguel.ojeda.sandonis@...il.com
Subject: Re: [PATCH 0/5] Rust abstractions for network device drivers
On Tue, 13 Jun 2023 13:53:21 +0900 FUJITA Tomonori wrote:
> This patchset adds minimum Rust abstractions for network device
> drivers and an example of a Rust network device driver, a simpler
> version of drivers/net/dummy.c.
>
> The dummy network device driver doesn't attach any bus such as PCI so
> the dependency is minimum. Hopefully, it would make reviewing easier.
>
> Thanks a lot for reviewing on RFC patchset at rust-for-linux ml.
> Hopefully, I've addressed all the issues.
First things first, what are the current expectations for subsystems
accepting rust code?
I was hoping someone from the Rust side is going to review this.
We try to review stuff within 48h at netdev, and there's no review :S
My immediate instinct is that I'd rather not merge toy implementations
unless someone within the netdev community can vouch for the code.
> rust/bindings/bindings_helper.h | 3 +
> rust/helpers.c | 23 ++
> rust/kernel/lib.rs | 3 +
> rust/kernel/net.rs | 5 +
> rust/kernel/net/dev.rs | 697 ++++++++++++++++++++++++++++++++
> samples/rust/Kconfig | 12 +
> samples/rust/Makefile | 1 +
> samples/rust/rust_net_dummy.rs | 81 ++++
> scripts/Makefile.build | 2 +-
You seem to create a rust/net/ directory without adding anything
to MAINTAINERS. Are we building a parallel directory structure?
Are the maintainers also different?
--
pw-bot: defer
Powered by blists - more mailing lists