[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Z6VVWT_vqb9EGGqv@cassiopeiae>
Date: Fri, 7 Feb 2025 01:35:37 +0100
From: Danilo Krummrich <dakr@...nel.org>
To: Lyude Paul <lyude@...hat.com>
Cc: rust-for-linux@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Maíra Canal <mairacanal@...eup.net>,
Miguel Ojeda <ojeda@...nel.org>,
Alex Gaynor <alex.gaynor@...il.com>,
Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <benno.lossin@...ton.me>,
Andreas Hindborg <a.hindborg@...nel.org>,
Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>,
Wedson Almeida Filho <wedsonaf@...il.com>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Xiangfei Ding <dingxiangfei2009@...il.com>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] rust/kernel: Add faux device bindings
On Thu, Feb 06, 2025 at 07:21:24PM -0500, Lyude Paul wrote:
> But yeah - I mean, faux::Registration::as_ref::<device::Device>() lets you get
> a device::Device which you can take a reference on using ARef. So you still
> can take a reference count to the device without us adding support for it
> explicitly was what I was getting at.
Yeah, that's true. But it would be nice to have a separate type faux::Device for
that, just like the C struct faux_device only exists to make this obvious given
that it's defined as follows.
struct faux_device {
struct device dev;
};
But I don't think we need that right away. Having a faux::Registration with
as_raw() should be enough for now.
Powered by blists - more mailing lists