Re: [PATCH -next] rust: fwctl: replace `__pinned_init` with `raw_try_init`

Mark Brown <[email protected]> Tue, 18 Aug 2026 15:16:21 +0100

Newsgroups	org.kernel.vger.linux-next,org.kernel.vger.rust-for-linux
Message-ID	<[email protected]>

On Tue, Aug 18, 2026 at 10:20:22AM -0300, Jason Gunthorpe wrote:
> On Tue, Aug 18, 2026 at 02:11:57PM +0100, Gary Guo wrote:

> > I'm not sure how this break everyone elses' branches? It only breaks linux-next
> > but that's why it exists in the first place, to catch tree
> > conflicts.

> linux-next is to catch missed things, you shouldn't use it to
> purposefully cause conflicts during the merge window..

> So for example introduce your new API and do some conversions, then
> remove the old API down the road after the merge window is a more
> expected work flow.

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.

signature.asc (application/pgp-signature, 488 B)