[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fd715b79-3ae2-44cb-8f51-7a903778274f@lunn.ch>
Date: Mon, 9 Oct 2023 16:31:04 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
Cc: Jiri Pirko <jiri@...nulli.us>,
FUJITA Tomonori <fujita.tomonori@...il.com>, netdev@...r.kernel.org,
rust-for-linux@...r.kernel.org, greg@...ah.com, tmgross@...ch.edu,
Wedson Almeida Filho <wedsonaf@...il.com>
Subject: Re: [PATCH net-next v3 3/3] net: phy: add Rust Asix PHY driver
> > I hope some sort of lessons learned, best practices and TODO list can
> > be distilled from the experience, to help guide the Rust Experiment.
>
> I appreciate that you are taking the time to have a look at the Rust
> support, but please note that most things you are mentioning are not
> really "lessons learned" -- they were things that were already known
> and/or worked on.
We are at the intersect of two worlds here. Maybe these issues are
well known in the linux for rust world, but they are not really known
to the netdev world, and to some extend the kernel developers /
maintainers world. We need to spread knowledge between each world.
So maybe this "lessons learned" is not really for the Rust people, but
for the netdev community, and kernel developers and Maintainers in
general?
Andrew
Powered by blists - more mailing lists