From: Alice Ryhl <aliceryhl@google.com>
To: Deborah Brouwer <deborah.brouwer@collabora.com>
Cc: "Alice Ryhl" <aliceryhl@google.com>,
"Danilo Krummrich" <dakr@kernel.org>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun@kernel.org>, "Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Trevor Gross" <tmgross@umich.edu>,
"Tamir Duberstein" <tamird@kernel.org>,
"Alexandre Courbot" <acourbot@nvidia.com>,
"Onur Özkan" <work@onurozkan.dev>,
"Jesung Yang" <y.j3ms.n@gmail.com>,
dri-devel@lists.freedesktop.org, rust-for-linux@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/2] drm/tyr: safely write GpuInfo to userspace
Date: Sat, 21 Nov 2026 14:12:45 +0000 [thread overview]
Message-ID: <20261121141247.142001-1-aliceryhl@google.com> (raw)
In-Reply-To: <20261020-b4-gpu_info_intobytes-v5-0-3e0c7c93223c@collabora.com>
On Tue, Oct 20, 2026 at 04:47:47PM -0700, Deborah Brouwer wrote:
> This series makes zerocopy and zerocopy_derive available to both the UAPI
> and bindings crates.
>
> It derives the zerocopy traits specifically for struct
> drm_panthor_gpu_info, allowing Tyr to safely copy this struct byte-for-
> byte into userspace memory.
>
> Signed-off-by: Deborah Brouwer <deborah.brouwer@collabora.com>
Applied to drm-rust-next. Thanks!
prev parent reply other threads:[~2026-11-21 14:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 23:47 Deborah Brouwer
2026-10-20 23:47 ` [PATCH v5 1/2] rust: add zerocopy to bindings and uapi Deborah Brouwer
2026-10-21 5:54 ` Alice Ryhl
2026-10-21 11:37 ` Miguel Ojeda
2026-10-21 11:44 ` Alice Ryhl
2026-10-29 15:36 ` Alice Ryhl
2026-11-20 10:54 ` Miguel Ojeda
2026-10-20 23:47 ` [PATCH v5 2/2] drm/tyr: safely write GpuInfo to userspace Deborah Brouwer
2026-11-21 14:12 ` Alice Ryhl [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=20261121141247.142001-1-aliceryhl@google.com \
--to=aliceryhl@google.com \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=airlied@gmail.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=deborah.brouwer@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=simona@ffwll.ch \
--cc=tamird@kernel.org \
--cc=tmgross@umich.edu \
--cc=work@onurozkan.dev \
--cc=y.j3ms.n@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®