From: Lyude Paul <lyude@redhat.com>
To: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
rust-for-linux@vger.kernel.org
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>
Subject: [PATCH v2 0/4] drm: Rust GEM bindings cleanup
Date: Tue, 13 May 2025 18:09:53 -0400 [thread overview]
Message-ID: <20250513221046.903358-1-lyude@redhat.com> (raw)
Just some patches to fix a handful of minor issues, some of which were already
mentioned on the mailing list. Some of these patches also make it just a
little bit easier to add the shmem bindings from Asahi in the future.
This patch series applies on top of dakr's nova-next branch:
https://gitlab.freedesktop.org/drm/nova/-/tree/nova-next
Lyude Paul (4):
rust: drm: gem: Use NonNull for Object::dev
rust: drm: gem: Refactor IntoGEMObject::from_gem_obj() to as_ref()
rust: drm: gem: s/into_gem_obj()/as_raw()/
rust: drm: gem: Implement AlwaysRefCounted for all gem objects
automatically
rust/kernel/drm/gem/mod.rs | 147 ++++++++++++++++++++-----------------
1 file changed, 78 insertions(+), 69 deletions(-)
base-commit: 61479ae38cb7bf6083de302598b7d491ec54168a
--
2.49.0
next reply other threads:[~2025-05-13 22:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 22:09 Lyude Paul [this message]
2025-05-13 22:09 ` [PATCH v2 1/4] rust: drm: gem: Use NonNull for Object::dev Lyude Paul
2025-05-13 22:09 ` [PATCH v2 2/4] rust: drm: gem: Refactor IntoGEMObject::from_gem_obj() to as_ref() Lyude Paul
2025-05-13 22:09 ` [PATCH v2 3/4] rust: drm: gem: s/into_gem_obj()/as_raw()/ Lyude Paul
2025-05-13 22:09 ` [PATCH v2 4/4] rust: drm: gem: Implement AlwaysRefCounted for all gem objects automatically Lyude Paul
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=20250513221046.903358-1-lyude@redhat.com \
--to=lyude@redhat.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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