* [PATCH] rust: drm: remove DRM device private data
@ 2026-11-18 18:07 Danilo Krummrich
2026-11-19 11:17 ` Alice Ryhl
0 siblings, 1 reply; 5+ messages in thread
From: Danilo Krummrich @ 2026-11-18 18:07 UTC (permalink / raw)
To: dakr, aliceryhl, airlied, simona, daniel.almeida, ojeda, boqun,
gary, bjorn3_gh, lossin, a.hindborg, tmgross, tamird, acourbot,
work
Cc: nova-gpu, dri-devel, linux-kernel, rust-for-linux
Driver::Data is owned by the reference-counted drm::Device and can
outlive device unregistration and driver unbind. Driver state belongs in
RegistrationData, whose lifetime ends with registration teardown.
The intended model is that, after drm_dev_unplug(), surviving DRM
objects (e.g. through remaining userspace handles) no longer require
access to the driver state. Thus Driver::RegistrationData is available
(and sufficient) for all DRM callbacks into the driver.
Remove Driver::Data, its storage and Deref implementation, and the
unused workqueue implementations that depend on it. Drop the data
initializer argument from UnregisteredDevice::new() and update its
callers.
Signed-off-by: Danilo Krummrich <dakr@kernel.org>
---
drivers/gpu/drm/nova/driver.rs | 3 +-
drivers/gpu/drm/tyr/driver.rs | 3 +-
rust/kernel/drm/device.rs | 128 ++-------------------------------
rust/kernel/drm/driver.rs | 3 -
rust/kernel/drm/gem/shmem.rs | 6 +-
5 files changed, 9 insertions(+), 134 deletions(-)
diff --git a/drivers/gpu/drm/nova/driver.rs b/drivers/gpu/drm/nova/driver.rs
index 44a52e60b3c7..df3f37d06861 100644
--- a/drivers/gpu/drm/nova/driver.rs
+++ b/drivers/gpu/drm/nova/driver.rs
@@ -71,7 +71,7 @@ fn probe<'bound>(
) -> impl PinInit<Self::Data<'bound>, Error> + 'bound {
try_pin_init!(Self::Data {
reg <- {
- let drm = drm::UnregisteredDevice::<Self>::new(adev, Ok(()))?;
+ let drm = drm::UnregisteredDevice::<Self>::new(adev)?;
let reg_data = DrmRegData {
api: NovaCoreApi::of(adev)?,
@@ -88,7 +88,6 @@ fn probe<'bound>(
#[vtable]
impl drm::Driver for NovaDriver {
- type Data = ();
type RegistrationData<'a> = DrmRegData<'a>;
type File = File;
type Object = gem::Object<NovaObject>;
diff --git a/drivers/gpu/drm/tyr/driver.rs b/drivers/gpu/drm/tyr/driver.rs
index c2b99d67369f..9caedd0fd130 100644
--- a/drivers/gpu/drm/tyr/driver.rs
+++ b/drivers/gpu/drm/tyr/driver.rs
@@ -148,7 +148,7 @@ fn probe<'bound>(
// other threads of execution.
unsafe { pdev.dma_set_mask_and_coherent(DmaMask::try_new(pa_bits)?)? };
- let unreg_dev = drm::UnregisteredDevice::<TyrDrmDriver>::new(pdev, Ok(()))?;
+ let unreg_dev = drm::UnregisteredDevice::<TyrDrmDriver>::new(pdev)?;
let mmu = Mmu::new(pdev.as_ref(), iomem.as_arc_borrow(), &gpu_info)?;
@@ -207,7 +207,6 @@ fn drop(self: Pin<&mut Self>) {}
#[vtable]
impl drm::Driver for TyrDrmDriver {
- type Data = ();
type RegistrationData<'drm> = TyrDrmRegistrationData<'drm>;
type File = TyrDrmFileData;
type Object = Bo;
diff --git a/rust/kernel/drm/device.rs b/rust/kernel/drm/device.rs
index 6b88ade28e24..774db3acb15a 100644
--- a/rust/kernel/drm/device.rs
+++ b/rust/kernel/drm/device.rs
@@ -22,12 +22,6 @@
types::{
NotThreadSafe,
Opaque, //
- },
- workqueue::{
- HasDelayedWork,
- HasWork,
- Work,
- WorkItem, //
}, //
};
use core::{
@@ -36,10 +30,7 @@
marker::PhantomData,
mem,
ops::Deref,
- ptr::{
- self,
- NonNull, //
- },
+ ptr::NonNull, //
};
#[cfg(CONFIG_DRM_LEGACY)]
@@ -167,7 +158,7 @@ const fn compute_features() -> u32 {
open: Some(drm::File::<T::File>::open_callback),
postclose: Some(drm::File::<T::File>::postclose_callback),
unload: None,
- release: Some(Device::<T>::release),
+ release: None,
master_set: None,
master_drop: None,
debugfs_init: None,
@@ -201,28 +192,18 @@ const fn compute_features() -> u32 {
/// Create a new `UnregisteredDevice` for a `drm::Driver`.
///
/// This can be used to create a [`Registration`](kernel::drm::Registration).
- pub fn new(
- dev: &T::ParentDevice<device::Bound>,
- data: impl PinInit<T::Data, Error>,
- ) -> Result<Self> {
+ pub fn new(dev: &T::ParentDevice<device::Bound>) -> Result<Self> {
// `__drm_dev_alloc` uses `kmalloc()` to allocate memory, hence ensure a `kmalloc()`
// compatible `Layout`.
let layout = Kmalloc::aligned_layout(Layout::new::<Device<T, Normal>>());
- // Use a temporary vtable without a `release` callback until `data` is initialized, so
- // init failure can release the DRM device without dropping uninitialized fields.
- let alloc_vtable = bindings::drm_driver {
- release: None,
- ..Self::VTABLE
- };
-
// SAFETY:
- // - `alloc_vtable` reference remains valid until no longer used,
- // - `dev` is valid by its type invarants,
+ // - The vtable has static storage duration.
+ // - `dev` is valid by its type invariants.
let raw_drm: *mut Device<T, Normal> = unsafe {
bindings::__drm_dev_alloc(
dev.as_ref().as_raw(),
- &alloc_vtable,
+ const { &Self::VTABLE },
layout.size(),
mem::offset_of!(Device<T, Normal>, dev),
)
@@ -230,25 +211,6 @@ pub fn new(
.cast();
let raw_drm = NonNull::new(from_err_ptr(raw_drm)?).ok_or(ENOMEM)?;
- // SAFETY: `raw_drm` is a valid pointer to `Self`, given that `__drm_dev_alloc` was
- // successful.
- let drm_dev = unsafe { Device::into_drm_device(raw_drm) };
-
- // SAFETY: `raw_drm` is a valid pointer to `Self`.
- let raw_data = unsafe { ptr::addr_of_mut!((*raw_drm.as_ptr()).data) };
-
- // SAFETY:
- // - `raw_data` is a valid pointer to uninitialized memory.
- // - `raw_data` will not move until it is dropped.
- unsafe { pin_init::raw_try_init(raw_data, data) }.inspect_err(|_| {
- // SAFETY: `__drm_dev_alloc()` was successful, hence `drm_dev` must be valid and the
- // refcount must be non-zero.
- unsafe { bindings::drm_dev_put(drm_dev) };
- })?;
-
- // SAFETY: `drm_dev` is still private to this function.
- unsafe { (*drm_dev).driver = const { &Self::VTABLE } };
-
// SAFETY: `raw_drm` is valid; no concurrent access before registration.
unsafe { (*raw_drm.as_ptr()).registration_data = UnsafeCell::new(NonNull::dangling()) };
@@ -274,7 +236,6 @@ pub fn new(
#[repr(C)]
pub struct Device<T: drm::Driver, C: DeviceContext = Normal> {
dev: Opaque<bindings::drm_device>,
- data: T::Data,
pub(super) registration_data: UnsafeCell<NonNull<T::RegistrationData<'static>>>,
_ctx: PhantomData<C>,
}
@@ -322,16 +283,6 @@ pub unsafe fn from_raw<'a>(ptr: *const bindings::drm_device) -> &'a Self {
unsafe { &*ptr.cast() }
}
- extern "C" fn release(ptr: *mut bindings::drm_device) {
- // SAFETY: `ptr` is a valid pointer to a `struct drm_device` and embedded in `Self`.
- let this = unsafe { Self::from_drm_device(ptr) };
-
- // SAFETY:
- // - When `release` runs it is guaranteed that there is no further access to `this`.
- // - `this` is valid for dropping.
- unsafe { core::ptr::drop_in_place(this) };
- }
-
/// Change the [`DeviceContext`] for a [`Device`].
///
/// # Safety
@@ -448,14 +399,6 @@ fn drop(&mut self) {
}
}
-impl<T: drm::Driver> Deref for Device<T> {
- type Target = T::Data;
-
- fn deref(&self) -> &Self::Target {
- &self.data
- }
-}
-
impl<T: drm::Driver> Deref for Device<T, Registered> {
type Target = Device<T>;
@@ -527,62 +470,3 @@ unsafe impl<T: drm::Driver, C: DeviceContext> Send for Device<T, C> {}
// SAFETY: A `drm::Device` can be shared among threads because all immutable methods are protected
// by the synchronization in `struct drm_device`.
unsafe impl<T: drm::Driver, C: DeviceContext> Sync for Device<T, C> {}
-
-impl<T: drm::Driver, const ID: u64> WorkItem<ID> for Device<T>
-where
- T::Data: WorkItem<ID, Pointer = ARef<Self>>,
- T::Data: HasWork<Self, ID>,
-{
- type Pointer = ARef<Self>;
-
- fn run(ptr: ARef<Self>) {
- T::Data::run(ptr);
- }
-}
-
-// SAFETY:
-//
-// - `raw_get_work` and `work_container_of` return valid pointers by relying on
-// `T::Data::raw_get_work` and `container_of`. In particular, `T::Data` is
-// stored inline in `drm::Device`, so the `container_of` call is valid.
-//
-// - The two methods are true inverses of each other: given `ptr: *mut
-// Device<T, C>`, `raw_get_work` will return a `*mut Work<Device<T, C>, ID>` through
-// `T::Data::raw_get_work` and given a `ptr: *mut Work<Device<T, C>, ID>`,
-// `work_container_of` will return a `*mut Device<T, C>` through `container_of`.
-unsafe impl<T, C, const ID: u64> HasWork<Self, ID> for Device<T, C>
-where
- T: drm::Driver,
- T::Data: HasWork<Self, ID>,
- C: DeviceContext,
-{
- unsafe fn raw_get_work(ptr: *mut Self) -> *mut Work<Self, ID> {
- // SAFETY: The caller promises that `ptr` points to a valid `Device<T, C>`.
- let data_ptr = unsafe { &raw mut (*ptr).data };
-
- // SAFETY: `data_ptr` is a valid pointer to `T::Data`.
- unsafe { T::Data::raw_get_work(data_ptr) }
- }
-
- unsafe fn work_container_of(ptr: *mut Work<Self, ID>) -> *mut Self {
- // SAFETY: The caller promises that `ptr` points at a `Work` field in
- // `T::Data`.
- let data_ptr = unsafe { T::Data::work_container_of(ptr) };
-
- // SAFETY: `T::Data` is stored as the `data` field in `Device<T, C>`.
- unsafe { crate::container_of!(data_ptr, Self, data) }
- }
-}
-
-// SAFETY: Our `HasWork<T, ID>` implementation returns a `work_struct` that is
-// stored in the `work` field of a `delayed_work` with the same access rules as
-// the `work_struct` owing to the bound on `T::Data: HasDelayedWork<Device<T, C>,
-// ID>`, which requires that `T::Data::raw_get_work` return a `work_struct` that
-// is inside a `delayed_work`.
-unsafe impl<T, C, const ID: u64> HasDelayedWork<Self, ID> for Device<T, C>
-where
- T: drm::Driver,
- T::Data: HasDelayedWork<Self, ID>,
- C: DeviceContext,
-{
-}
diff --git a/rust/kernel/drm/driver.rs b/rust/kernel/drm/driver.rs
index f6db91e81e79..7b76e6abed9f 100644
--- a/rust/kernel/drm/driver.rs
+++ b/rust/kernel/drm/driver.rs
@@ -106,9 +106,6 @@ pub trait AllocImpl: super::private::Sealed + drm::gem::IntoGEMObject {
/// drm_driver` to be registered in the DRM subsystem.
#[vtable]
pub trait Driver {
- /// Context data associated with the DRM driver
- type Data: Sync + Send;
-
/// Data owned by the [`Registration`] and accessible within a
/// [`RegistrationGuard`](drm::RegistrationGuard) critical section via
/// [`Device::registration_data_with()`](drm::Device::registration_data_with).
diff --git a/rust/kernel/drm/gem/shmem.rs b/rust/kernel/drm/gem/shmem.rs
index ed13e21d06cf..3a72fb21eeaa 100644
--- a/rust/kernel/drm/gem/shmem.rs
+++ b/rust/kernel/drm/gem/shmem.rs
@@ -589,8 +589,6 @@ mod tests {
// The bare minimum needed to create a fake drm driver for kunit
- #[pin_data]
- struct KunitData {}
struct KunitDriver;
struct KunitFile;
#[pin_data]
@@ -627,7 +625,6 @@ fn new(
#[vtable]
impl drm::Driver for KunitDriver {
- type Data = KunitData;
type RegistrationData<'a> = ();
type File = KunitFile;
type Object = Object<KunitObject>;
@@ -639,10 +636,9 @@ impl drm::Driver for KunitDriver {
fn create_drm_dev() -> Result<(faux::Registration, UnregisteredDevice<KunitDriver>)> {
// Create a faux DRM device so we can test gem object creation.
- let data = try_pin_init!(KunitData {});
let reg = faux::Registration::new(c"Kunit", None)?;
let fdev = reg.as_ref();
- let drm = UnregisteredDevice::new(fdev, data)?;
+ let drm = UnregisteredDevice::new(fdev)?;
Ok((reg, drm))
}
base-commit: e55a991e09e3b44f0b0d8206bb523dc57c086341
--
2.56.1
^ permalink raw reply related [flat|nested] 5+ messages in thread* Re: [PATCH] rust: drm: remove DRM device private data
2026-11-18 18:07 [PATCH] rust: drm: remove DRM device private data Danilo Krummrich
@ 2026-11-19 11:17 ` Alice Ryhl
2026-11-19 11:24 ` Gary Guo
0 siblings, 1 reply; 5+ messages in thread
From: Alice Ryhl @ 2026-11-19 11:17 UTC (permalink / raw)
To: Danilo Krummrich
Cc: Alice Ryhl, airlied, simona, daniel.almeida, ojeda, boqun, gary,
bjorn3_gh, lossin, a.hindborg, tmgross, tamird, acourbot, work,
nova-gpu, dri-devel, linux-kernel, rust-for-linux
On Wed, Nov 18, 2026 at 07:07:35PM +0100, Danilo Krummrich wrote:
> Driver::Data is owned by the reference-counted drm::Device and can
> outlive device unregistration and driver unbind. Driver state belongs in
> RegistrationData, whose lifetime ends with registration teardown.
>
> The intended model is that, after drm_dev_unplug(), surviving DRM
> objects (e.g. through remaining userspace handles) no longer require
> access to the driver state. Thus Driver::RegistrationData is available
> (and sufficient) for all DRM callbacks into the driver.
>
> Remove Driver::Data, its storage and Deref implementation, and the
> unused workqueue implementations that depend on it. Drop the data
> initializer argument from UnregisteredDevice::new() and update its
> callers.
>
> Signed-off-by: Danilo Krummrich <dakr@kernel.org>
Makes sense to me. Both in-tree users had `type Data = ()` anyway, and
nothing uses the `WorkItem`/`HasWork` impls on `drm::Device`, so this is
a pure simplification.
Reviewed-by: Alice Ryhl <aliceryhl@google.com>
One small suggestion below.
> - release: Some(Device::<T>::release),
> + release: None,
[...]
> #[repr(C)]
> pub struct Device<T: drm::Driver, C: DeviceContext = Normal> {
> dev: Opaque<bindings::drm_device>,
> - data: T::Data,
> pub(super) registration_data: UnsafeCell<NonNull<T::RegistrationData<'static>>>,
> _ctx: PhantomData<C>,
> }
With `release` gone, nothing ever runs `drop_in_place()` on the Rust
side of `Device` anymore. That's fine today since all remaining fields
are trivially droppable, but it is now an implicit requirement on the
struct: anyone adding a field with a `Drop` impl (or a pinned field
that needs a destructor) would silently leak it.
Could you add a short comment on the struct along the lines of "no
`release` callback is installed, so no field of this struct may require
dropping"? That way the next person adding a field knows they have to
bring back the `release` callback.
(For what it's worth, I checked the lifetime-parameterized `File`
series [1] against this: `open_count`/`open_count_wq` are both
droppable without a destructor, and the two merge cleanly, so no
ordering constraint there as far as I can tell.)
[1] https://lore.kernel.org/r/20261118163203.2483856-1-dakr@kernel.org
Alice
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [PATCH] rust: drm: remove DRM device private data
2026-11-19 11:17 ` Alice Ryhl
@ 2026-11-19 11:24 ` Gary Guo
2026-11-19 11:49 ` Alice Ryhl
0 siblings, 1 reply; 5+ messages in thread
From: Gary Guo @ 2026-11-19 11:24 UTC (permalink / raw)
To: Alice Ryhl, Danilo Krummrich
Cc: airlied, simona, daniel.almeida, ojeda, boqun, gary, bjorn3_gh,
lossin, a.hindborg, tmgross, tamird, acourbot, work, nova-gpu,
dri-devel, linux-kernel, rust-for-linux
On Thu Nov 19, 2026 at 11:17 AM GMT, Alice Ryhl wrote:
> On Wed, Nov 18, 2026 at 07:07:35PM +0100, Danilo Krummrich wrote:
>> Driver::Data is owned by the reference-counted drm::Device and can
>> outlive device unregistration and driver unbind. Driver state belongs in
>> RegistrationData, whose lifetime ends with registration teardown.
>>
>> The intended model is that, after drm_dev_unplug(), surviving DRM
>> objects (e.g. through remaining userspace handles) no longer require
>> access to the driver state. Thus Driver::RegistrationData is available
>> (and sufficient) for all DRM callbacks into the driver.
>>
>> Remove Driver::Data, its storage and Deref implementation, and the
>> unused workqueue implementations that depend on it. Drop the data
>> initializer argument from UnregisteredDevice::new() and update its
>> callers.
>>
>> Signed-off-by: Danilo Krummrich <dakr@kernel.org>
>
> Makes sense to me. Both in-tree users had `type Data = ()` anyway, and
> nothing uses the `WorkItem`/`HasWork` impls on `drm::Device`, so this is
> a pure simplification.
>
> Reviewed-by: Alice Ryhl <aliceryhl@google.com>
>
> One small suggestion below.
>
>> - release: Some(Device::<T>::release),
>> + release: None,
>
> [...]
>
>> #[repr(C)]
>> pub struct Device<T: drm::Driver, C: DeviceContext = Normal> {
>> dev: Opaque<bindings::drm_device>,
>> - data: T::Data,
>> pub(super) registration_data: UnsafeCell<NonNull<T::RegistrationData<'static>>>,
>> _ctx: PhantomData<C>,
>> }
>
> With `release` gone, nothing ever runs `drop_in_place()` on the Rust
> side of `Device` anymore. That's fine today since all remaining fields
> are trivially droppable, but it is now an implicit requirement on the
> struct: anyone adding a field with a `Drop` impl (or a pinned field
> that needs a destructor) would silently leak it.
>
> Could you add a short comment on the struct along the lines of "no
> `release` callback is installed, so no field of this struct may require
> dropping"? That way the next person adding a field knows they have to
> bring back the `release` callback.
>
> (For what it's worth, I checked the lifetime-parameterized `File`
> series [1] against this: `open_count`/`open_count_wq` are both
> droppable without a destructor, and the two merge cleanly, so no
> ordering constraint there as far as I can tell.)
Instead of a comment, a const assertion of !needs_drop would be better.
Best,
Gary
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [PATCH] rust: drm: remove DRM device private data
2026-11-19 11:24 ` Gary Guo
@ 2026-11-19 11:49 ` Alice Ryhl
2026-11-19 17:28 ` Danilo Krummrich
0 siblings, 1 reply; 5+ messages in thread
From: Alice Ryhl @ 2026-11-19 11:49 UTC (permalink / raw)
To: Gary Guo
Cc: Danilo Krummrich, airlied, simona, daniel.almeida, ojeda, boqun,
bjorn3_gh, lossin, a.hindborg, tmgross, tamird, acourbot, work,
nova-gpu, dri-devel, linux-kernel, rust-for-linux
On Thu, Nov 19, 2026 at 12:25 PM Gary Guo <gary@garyguo.net> wrote:
>
> On Thu Nov 19, 2026 at 11:17 AM GMT, Alice Ryhl wrote:
> > On Wed, Nov 18, 2026 at 07:07:35PM +0100, Danilo Krummrich wrote:
> >> Driver::Data is owned by the reference-counted drm::Device and can
> >> outlive device unregistration and driver unbind. Driver state belongs in
> >> RegistrationData, whose lifetime ends with registration teardown.
> >>
> >> The intended model is that, after drm_dev_unplug(), surviving DRM
> >> objects (e.g. through remaining userspace handles) no longer require
> >> access to the driver state. Thus Driver::RegistrationData is available
> >> (and sufficient) for all DRM callbacks into the driver.
> >>
> >> Remove Driver::Data, its storage and Deref implementation, and the
> >> unused workqueue implementations that depend on it. Drop the data
> >> initializer argument from UnregisteredDevice::new() and update its
> >> callers.
> >>
> >> Signed-off-by: Danilo Krummrich <dakr@kernel.org>
> >
> > Makes sense to me. Both in-tree users had `type Data = ()` anyway, and
> > nothing uses the `WorkItem`/`HasWork` impls on `drm::Device`, so this is
> > a pure simplification.
> >
> > Reviewed-by: Alice Ryhl <aliceryhl@google.com>
> >
> > One small suggestion below.
> >
> >> - release: Some(Device::<T>::release),
> >> + release: None,
> >
> > [...]
> >
> >> #[repr(C)]
> >> pub struct Device<T: drm::Driver, C: DeviceContext = Normal> {
> >> dev: Opaque<bindings::drm_device>,
> >> - data: T::Data,
> >> pub(super) registration_data: UnsafeCell<NonNull<T::RegistrationData<'static>>>,
> >> _ctx: PhantomData<C>,
> >> }
> >
> > With `release` gone, nothing ever runs `drop_in_place()` on the Rust
> > side of `Device` anymore. That's fine today since all remaining fields
> > are trivially droppable, but it is now an implicit requirement on the
> > struct: anyone adding a field with a `Drop` impl (or a pinned field
> > that needs a destructor) would silently leak it.
> >
> > Could you add a short comment on the struct along the lines of "no
> > `release` callback is installed, so no field of this struct may require
> > dropping"? That way the next person adding a field knows they have to
> > bring back the `release` callback.
> >
> > (For what it's worth, I checked the lifetime-parameterized `File`
> > series [1] against this: `open_count`/`open_count_wq` are both
> > droppable without a destructor, and the two merge cleanly, so no
> > ordering constraint there as far as I can tell.)
>
> Instead of a comment, a const assertion of !needs_drop would be better.
Good idea
Alice
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [PATCH] rust: drm: remove DRM device private data
2026-11-19 11:49 ` Alice Ryhl
@ 2026-11-19 17:28 ` Danilo Krummrich
0 siblings, 0 replies; 5+ messages in thread
From: Danilo Krummrich @ 2026-11-19 17:28 UTC (permalink / raw)
To: Alice Ryhl
Cc: Gary Guo, airlied, simona, daniel.almeida, ojeda, boqun,
bjorn3_gh, lossin, a.hindborg, tmgross, tamird, acourbot, work,
nova-gpu, dri-devel, linux-kernel, rust-for-linux
On Thu Nov 19, 2026 at 12:49 PM CET, Alice Ryhl wrote:
> Good idea
Indeed, what do you think about this?
diff --git a/rust/kernel/drm/device.rs b/rust/kernel/drm/device.rs
index 774db3acb15a..8c48dcfdecec 100644
--- a/rust/kernel/drm/device.rs
+++ b/rust/kernel/drm/device.rs
@@ -158,7 +158,11 @@ const fn compute_features() -> u32 {
open: Some(drm::File::<T::File>::open_callback),
postclose: Some(drm::File::<T::File>::postclose_callback),
unload: None,
- release: None,
+ release: {
+ // The DRM core frees the device without running a Rust destructor.
+ const_assert!(!mem::needs_drop::<Device<T, Normal>>());
+ None
+ },
master_set: None,
master_drop: None,
debugfs_init: None,
^ permalink raw reply related [flat|nested] 5+ messages in thread
end of thread, other threads:[~2026-11-19 17:28 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-11-18 18:07 [PATCH] rust: drm: remove DRM device private data Danilo Krummrich
2026-11-19 11:17 ` Alice Ryhl
2026-11-19 11:24 ` Gary Guo
2026-11-19 11:49 ` Alice Ryhl
2026-11-19 17:28 ` Danilo Krummrich
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox