From: "Danilo Krummrich" <dakr@kernel.org>
To: <dri-devel@lists.freedesktop.org>, <nova-gpu@lists.linux.dev>
Cc: "Alice Ryhl" <aliceryhl@google.com>,
"Alexandre Courbot" <acourbot@nvidia.com>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"John Hubbard" <jhubbard@nvidia.com>,
"Eliot Courtney" <ecourtney@nvidia.com>,
"Joel Fernandes" <joelagnelf@nvidia.com>,
"Alistair Popple" <apopple@nvidia.com>,
"Timur Tabi" <ttabi@nvidia.com>, "Zhi Wang" <zhiw@nvidia.com>,
"Lyude Paul" <lyude@redhat.com>, "Gary Guo" <gary@garyguo.net>,
"Philipp Stanner" <phasta@mailbox.org>,
"Deborah Brouwer" <deborah.brouwer@collabora.com>,
"Beata Michalska" <beata.michalska@arm.com>,
"Boris Brezillon" <boris.brezillon@collabora.com>,
"Steven Price" <steven.price@arm.com>,
"Onur Özkan" <work@onurozkan.dev>, "Janne Grunau" <j@jannau.net>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Miguel Ojeda" <ojeda@kernel.org>,
rust-for-linux@vger.kernel.org
Subject: drm-rust: process change announcement
Date: Sun, 26 Apr 2026 23:33:01 +0200 [thread overview]
Message-ID: <DI3EPKNRWMQJ.17YVN5V0VBKLR@kernel.org> (raw)
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
reply other threads:[~2026-04-26 21:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=DI3EPKNRWMQJ.17YVN5V0VBKLR@kernel.org \
--to=dakr@kernel.org \
--cc=acourbot@nvidia.com \
--cc=airlied@gmail.com \
--cc=aliceryhl@google.com \
--cc=apopple@nvidia.com \
--cc=beata.michalska@arm.com \
--cc=boris.brezillon@collabora.com \
--cc=daniel.almeida@collabora.com \
--cc=deborah.brouwer@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=ecourtney@nvidia.com \
--cc=gary@garyguo.net \
--cc=j@jannau.net \
--cc=jhubbard@nvidia.com \
--cc=joelagnelf@nvidia.com \
--cc=lyude@redhat.com \
--cc=nova-gpu@lists.linux.dev \
--cc=ojeda@kernel.org \
--cc=phasta@mailbox.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=simona@ffwll.ch \
--cc=steven.price@arm.com \
--cc=ttabi@nvidia.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.