From: "Danilo Krummrich" <dakr@kernel.org>
To: "Nicolás Antinori" <nico.antinori.7@gmail.com>
Cc: "Alistair Popple" <apopple@nvidia.com>,
"Alice Ryhl" <aliceryhl@google.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alexandre Courbot" <acourbot@nvidia.com>,
"David Airlie" <airlied@gmail.com>,
"Shuah Khan" <skhan@linuxfoundation.org>,
"Simona Vetter" <simona@ffwll.ch>, "Gary Guo" <gary@garyguo.net>,
"Onur Özkan" <work@onurozkan.dev>,
"Tamir Duberstein" <tamird@kernel.org>,
"Trevor Gross" <tmgross@umich.edu>,
linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linux.dev,
dri-devel@lists.freedesktop.org, rust-for-linux@vger.kernel.org,
nova-gpu@lists.linux.dev
Subject: Re: [PATCH] gpu: nova-core: parse structs via zerocopy
Date: Mon, 22 Jun 2026 23:02:59 +0200 [thread overview]
Message-ID: <DJFVRMR67B0W.2AJBHU1PWDPFT@kernel.org> (raw)
In-Reply-To: <DJFUZJYZHOT1.M74T83PJE8GM@gmail.com>
On Mon Jun 22, 2026 at 10:26 PM CEST, Nicolás Antinori wrote:
> I did my work on rust-next [1] because drm-rust-next does not have the
> zerocopy crate present yet [2]. linux-next contains both zerocopy [3]
> and the new users of transmute::FromBytes if I am not mistaken (BitToken,
> PciRomHeader, and PmuLookupTableEntry), so I can make the changes there.
The drm-rust tree is a bit special, as it remains open for contributions even
after it has been tagged for inclusion into Linus's (including throughout the
merge window). However, all changes staged in drm-rust-next are not going into
linux-next until -rc1 is released.
IOW, until -rc1 is released this may or may not resolve all conflicts with
drm-rust-next. Once -rc1 is released, it is backmerged into drm-rust-next and
drm-rust-next is picked up by linux-next again.
Usually all of this remains rather transparent to contributors, but you hit the
case of using a new feature introduced through another tree before drm-rust-next
caught up with Linus's tree (which will happen next Sunday).
Before drm-rust-next caught up, this patch can't be applied anyways, so all
good.
> I am fairly new to kernel development, I apologize for the mix-up.
No worries, you did nothing wrong; thanks for the contribution!
- Danilo
prev parent reply other threads:[~2026-06-22 21:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-21 14:36 [PATCH] gpu: nova-core: parse structs via zerocopy Nicolás Antinori
2026-06-22 7:45 ` Alistair Popple
2026-06-22 20:26 ` Nicolás Antinori
2026-06-22 21:02 ` Danilo Krummrich [this message]
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=DJFVRMR67B0W.2AJBHU1PWDPFT@kernel.org \
--to=dakr@kernel.org \
--cc=acourbot@nvidia.com \
--cc=airlied@gmail.com \
--cc=aliceryhl@google.com \
--cc=apopple@nvidia.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gary@garyguo.net \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=nico.antinori.7@gmail.com \
--cc=nova-gpu@lists.linux.dev \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=simona@ffwll.ch \
--cc=skhan@linuxfoundation.org \
--cc=tamird@kernel.org \
--cc=tmgross@umich.edu \
--cc=work@onurozkan.dev \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox