* drm-rust: process change announcement
@ 2026-04-26 21:33 Danilo Krummrich
0 siblings, 0 replies; only message in thread
From: Danilo Krummrich @ 2026-04-26 21:33 UTC (permalink / raw)
To: dri-devel, nova-gpu
Cc: Alice Ryhl, Alexandre Courbot, Daniel Almeida, John Hubbard,
Eliot Courtney, Joel Fernandes, Alistair Popple, Timur Tabi,
Zhi Wang, Lyude Paul, Gary Guo, Philipp Stanner, Deborah Brouwer,
Beata Michalska, Boris Brezillon, Steven Price, Onur Özkan,
Janne Grunau, David Airlie, Simona Vetter, Miguel Ojeda,
rust-for-linux
As already mentioned in [1], 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 one after that.
Fixes for code that landed in drm-rust-next 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.
Please also see the updated documentation in [2] and [3].
Also note that commits merged into drm-rust-next after -rc6 will not be present
in linux-next until -rc1 of the next cycle.
- Danilo
[1] https://lore.kernel.org/all/DHUXFAD38G5Y.6X6QNTANYNGH@kernel.org/
[2] https://drm.pages.freedesktop.org/maintainer-tools/repositories/drm-rust.html
[3] https://drm.pages.freedesktop.org/maintainer-tools/committer/committer-drm-rust.html
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2026-04-26 21:33 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-04-26 21:33 drm-rust: process change announcement Danilo Krummrich
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox