[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87y1i91pgo.fsf@meer.lwn.net>
Date: Thu, 17 Aug 2023 12:41:27 -0600
From: Jonathan Corbet <corbet@....net>
To: Jakub Kicinski <kuba@...nel.org>, Michele Dalle Rive
<dallerivemichele@...il.com>
Cc: Andrew Lunn <andrew@...n.ch>, Greg KH <gregkh@...uxfoundation.org>,
Miguel Ojeda <ojeda@...nel.org>, Alex Gaynor <alex.gaynor@...il.com>,
Wedson Almeida Filho <wedsonaf@...il.com>, "David S. Miller"
<davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Paolo Abeni
<pabeni@...hat.com>, Boqun Feng <boqun.feng@...il.com>, Gary Guo
<gary@...yguo.net>, Björn Roy Baron
<bjorn3_gh@...tonmail.com>, Benno
Lossin <benno.lossin@...ton.me>, Alice Ryhl <aliceryhl@...gle.com>, Davide
Rovelli <davide.rovelli@....ch>, rust-for-linux@...r.kernel.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
patches@...ts.linux.dev
Subject: Re: [RFC PATCH 0/7] Rust Socket abstractions
Jakub Kicinski <kuba@...nel.org> writes:
> I thought the Rust was just shaking up the languages we use, not the
> fundamentals on how this project operates :|
I don't think this little episode has anything to do with Rust, really;
certainly we've had no shortage of companies wanting support for
out-of-tree modules written in C over the years.
Instead, this is just the sort of thing you see when people who are new
to our community learn - the hard way, sometimes - how kernel
development works. Rust seems likely to bring in a fair number of new
developers, which is great, but we're going to have to help them learn
their way around.
Thanks,
jon
Powered by blists - more mailing lists