Re: [PATCH -next] rust: fwctl: replace `__pinned_init` with `raw_try_init`
"Danilo Krummrich" <[email protected]>
| Newsgroups | org.kernel.vger.linux-next,org.kernel.vger.rust-for-linux |
|---|---|
| Message-ID | <[email protected]> |
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.