Re: [PATCH v2 0/3] rust: add `bitfield!` macro

["Danilo Krummrich" <dakr@kernel.org>]

On Thu Apr 16, 2026 at 1:22 AM CEST, John Hubbard wrote:
> Can we please put this into your drm-rust-next-staging ASAP? I don't
> think we have any comments that would really need to hold that up.

I would like to see the first patch being split up and we also need to agree the
merge strategy for this series and obtain the corresponding ACKs first.

That said, I'm not a huge fan of the drm-rust-next-staging thing. It started out
as part of Alex' (private) process of staging patches he's about to pick up
(which is fine of course).

But now it seems to develop into some semi-official "shadow infrastructure" for
when the drm-rust tree is closed after -rc6 and during the merge window, and
it's not part of the official drm-rust workflow and other maintainers don't have
oversight of it.

So, in order to not motivate workarounds, starting from the next cycle, the
drm-rust-next branch will be open for new features at all times.

Consequently, all patches applied to drm-rust-next after -rc6 do not target the
upcoming merge window, but the next one.

Fixes for code that is within drm-rust-next and was merged before -rc6 have to
go into drm-rust-next-fixes.

drm-rust-fixes will continue to be the target for fixes for the current -rc.

I will update all corresponding documentation in the next days and send another
announcement mail, so it is not only this one buried in a thread where no one
expects it. :)

- Danilo