[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <DBCWVWUNRR05.37YH3UZW1R0PW@kernel.org>
Date: Tue, 15 Jul 2025 22:29:48 +0200
From: "Danilo Krummrich" <dakr@...nel.org>
To: <gregkh@...uxfoundation.org>, <rafael@...nel.org>, <ojeda@...nel.org>,
<alex.gaynor@...il.com>, <boqun.feng@...il.com>, <gary@...yguo.net>,
<bjorn3_gh@...tonmail.com>, <lossin@...nel.org>, <a.hindborg@...nel.org>,
<aliceryhl@...gle.com>, <tmgross@...ch.edu>,
<daniel.almeida@...labora.com>, <m.wilczynski@...sung.com>
Cc: <rust-for-linux@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] rust: devres: provide an accessor for the device
On Sun Jul 13, 2025 at 8:26 PM CEST, Danilo Krummrich wrote:
> Provide an accessor for the Device a Devres instance has been created
> with.
>
> For instance, this is useful when registrations want to provide a
> &Device<Bound> for a scope that is protected by Devres.
>
> Suggested-by: Benno Lossin <lossin@...nel.org>
> Signed-off-by: Danilo Krummrich <dakr@...nel.org>
Applied to driver-core-testing, thanks!
Powered by blists - more mailing lists