From: Jason Gunthorpe <jgg@nvidia.com>
To: Mark Brown <broonie@kernel.org>
Cc: "Gary Guo" <gary@garyguo.net>, "Miguel Ojeda" <ojeda@kernel.org>,
"Dave Jiang" <dave.jiang@intel.com>,
"Saeed Mahameed" <saeedm@nvidia.com>,
"Zhi Wang" <zhiw@nvidia.com>, "Benno Lossin" <lossin@kernel.org>,
linux-next@vger.kernel.org, "Jonathan Cameron" <jic23@kernel.org>,
rust-for-linux@vger.kernel.org, "Boqun Feng" <boqun@kernel.org>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"Tamir Duberstein" <tamird@kernel.org>,
"Alexandre Courbot" <acourbot@nvidia.com>,
"Onur Özkan" <work@onurozkan.dev>
Subject: Re: [PATCH -next] rust: fwctl: replace `__pinned_init` with `raw_try_init`
Date: Tue, 18 Aug 2026 11:23:00 -0300 [thread overview]
Message-ID: <20260818142300.GE5432@nvidia.com> (raw)
In-Reply-To: <0e0c9ee9-ce44-49cf-b5c5-3764f260f1b5@sirena.org.uk>
On Tue, Aug 18, 2026 at 03:16:21PM +0100, Mark Brown wrote:
> I'd been under the impression that the reason this was happening a lot
> with Rust was something to do with how the language works.
My impression is the rust team is still learning how best to apply
rust to linux. So things land and get changed around with a healthy
does of compile breaking changes. In a certain sense they are building
a unique kernel specific dialect of rust as they go.
It's fine, and this particular case is managable, but my main point is
as rust increases in scope a more accommodating process is needed to
maintain the general kernel work flow.
Jason
next prev parent reply other threads:[~2026-08-18 14:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 10:53 [PATCH -next] rust: fwctl: replace `__pinned_init` with `raw_try_init` Miguel Ojeda
2026-08-18 12:55 ` Jason Gunthorpe
2026-08-18 13:11 ` Gary Guo
2026-08-18 13:20 ` Jason Gunthorpe
2026-08-18 13:40 ` Gary Guo
2026-08-18 14:16 ` Mark Brown
2026-08-18 14:23 ` Jason Gunthorpe [this message]
2026-08-18 20:37 ` Miguel Ojeda
2026-08-18 20:46 ` Jason Gunthorpe
2026-08-18 14:30 ` Danilo Krummrich
2026-08-18 14:44 ` Mark Brown
2026-08-18 20:33 ` Miguel Ojeda
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=20260818142300.GE5432@nvidia.com \
--to=jgg@nvidia.com \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=broonie@kernel.org \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=dave.jiang@intel.com \
--cc=gary@garyguo.net \
--cc=jic23@kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=saeedm@nvidia.com \
--cc=tamird@kernel.org \
--cc=tmgross@umich.edu \
--cc=work@onurozkan.dev \
--cc=zhiw@nvidia.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.