From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 1E96D21CC5A; Mon, 22 Jun 2026 21:03:04 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782162186; cv=none; b=et23G/wvRXtV2qje4hR3f+FPJjfRH7J91dEPoWPYz/pjN0pzxq5hpG0LuD6rFXvEa+X2BxTwsxh2kOpDCOxUZV6jCZ1PUytZnTnwsicVDPE7fn2MZWDB67D1g7miG6gFTc69G7k+DTvV6jpxK3xBPtwrDYtuwTg1IysJ44QWrRs= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782162186; c=relaxed/simple; bh=d6lKqpalFTpc0qx48Y3a+XrmMGn1yQwsZp9Dj+auQHc=; h=Mime-Version:Content-Type:Date:Message-Id:Subject:Cc:To:From: References:In-Reply-To; b=js633H9737azEQkLQJj07VYseJ2MrxuVglshsP+N3tAb3/T3B+tORi7XKlTldfMoz1EGyX5o7dn+zcwZ5iHTG5SQm24CLeqRoF05wL0E2XIIV6HSOtAK8OaAowXT2wa1NLMNp1E48/pMgjDwj/lhLCaeZT9CZPLzw65pF2yUAVM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=k4wio2Jh; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="k4wio2Jh" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 067231F000E9; Mon, 22 Jun 2026 21:03:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1782162184; bh=d6lKqpalFTpc0qx48Y3a+XrmMGn1yQwsZp9Dj+auQHc=; h=Date:Subject:Cc:To:From:References:In-Reply-To; b=k4wio2Jhdpjb74Ar8WeFUpruVWMmqR3pAhH6RCtnBruIoMFRjDZHcysDRykC+1QFM vLCmbIAFn2859e7DU/kJgp7J49eXDL5bqSnunkoNCWszcWa2LLi7OsYfFEWbmaMOXw TUCXMR+Rd4bKeE1x9c2a735uPy/zG7O45H250F8SijeFge1qdpsq0Axng8YwplHuJR d9FMpibn4JTWJNXKJGJuIujhRUjT2ge+NCN/Un5/WL8lJJH0KjrCXYdqkS1afRZRdB nL0LQRe08UDlfsWTOA8Rqy1pG83fYHn9SXZX/J88lOqej/uBmhi7k9YL7fuuRk2P/h q8yAeaM088OWw== Precedence: bulk X-Mailing-List: nova-gpu@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Mon, 22 Jun 2026 23:02:59 +0200 Message-Id: Subject: Re: [PATCH] gpu: nova-core: parse structs via zerocopy Cc: "Alistair Popple" , "Alice Ryhl" , "Miguel Ojeda" , "Alexandre Courbot" , "David Airlie" , "Shuah Khan" , "Simona Vetter" , "Gary Guo" , =?utf-8?q?Onur_=C3=96zkan?= , "Tamir Duberstein" , "Trevor Gross" , , , , , To: =?utf-8?q?Nicol=C3=A1s_Antinori?= From: "Danilo Krummrich" References: <20260621143647.264770-1-nico.antinori.7@gmail.com> In-Reply-To: On Mon Jun 22, 2026 at 10:26 PM CEST, Nicol=C3=A1s 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]=20 > 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 ev= en after it has been tagged for inclusion into Linus's (including throughout t= he merge window). However, all changes staged in drm-rust-next are not going i= nto 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 a= nd 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