Re: [PATCH] gpu: nova-core: parse structs via zerocopy

"Danilo Krummrich" <[email protected]>
Newsgroups dev.linux.lists.nova-gpu,dev.linux.lists.linux-kernel-mentees,org.freedesktop.lists.dri-devel,org.kernel.vger.linux-kernel,org.kernel.vger.rust-for-linux
Message-ID <[email protected]>
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.