Rust for Linux List
 help / color / mirror / Atom feed
From: "Danilo Krummrich" <dakr@kernel.org>
To: "Mark Brown" <broonie@kernel.org>
Cc: "Jason Gunthorpe" <jgg@nvidia.com>, "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>,
	"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 16:30:16 +0200	[thread overview]
Message-ID: <DKS53ZVUOF01.12DKD5ITC77TI@kernel.org> (raw)
In-Reply-To: <0e0c9ee9-ce44-49cf-b5c5-3764f260f1b5@sirena.org.uk>

On Tue Aug 18, 2026 at 4:16 PM CEST, Mark Brown wrote:
> So are these updates that are requiring frequent patching up aren't
> forced as a result of some Rust language thing but rather deliberate
> decisions?  In that case I tend to agree with Jason, I'd not expect to
> see changes like these coming in during the merge window without a
> strong reason, and with C changes like these would normally be done in a
> much more coordinated fashion - for example an overlap period like Jason
> suggests, possibly with shared branches.
>
> 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.

In general that is the case, the stronger type system makes it more difficult to
avoid conflicts by preserving compatible APIs (which is also one reason why I
work a lot with shared signed tags).

In this specific case it is indeed what Gary already explained; the API was
removed and unexpectedly gained a new user.

  parent reply	other threads:[~2026-08-18 14:30 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
2026-08-18 20:37           ` Miguel Ojeda
2026-08-18 20:46             ` Jason Gunthorpe
2026-08-18 14:30         ` Danilo Krummrich [this message]
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=DKS53ZVUOF01.12DKD5ITC77TI@kernel.org \
    --to=dakr@kernel.org \
    --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=daniel.almeida@collabora.com \
    --cc=dave.jiang@intel.com \
    --cc=gary@garyguo.net \
    --cc=jgg@nvidia.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox