[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <DDV0AYWXTCL5.2QDTJI55Q87CJ@kernel.org>
Date: Wed, 29 Oct 2025 19:10:27 +0100
From: "Danilo Krummrich" <dakr@...nel.org>
To: <gregkh@...uxfoundation.org>, <rafael@...nel.org>,
<bhelgaas@...gle.com>, <kwilczynski@...nel.org>,
<david.m.ertman@...el.com>, <ira.weiny@...el.com>, <leon@...nel.org>,
<acourbot@...dia.com>, <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>, <pcolberg@...hat.com>
Cc: <rust-for-linux@...r.kernel.org>, <linux-pci@...r.kernel.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/8] Device::drvdata() and driver/driver interaction
(auxiliary)
On Tue Oct 21, 2025 at 12:34 AM CEST, Danilo Krummrich wrote:
Applied to driver-core-testing, thanks!
> Danilo Krummrich (8):
> rust: device: narrow the generic of drvdata_obtain()
> rust: device: introduce Device::drvdata()
[ * Remove unnecessary `const _: ()` block,
* rename type_id_{store,match}() to {set,match}_type_id(),
* assert size_of::<bindings::driver_type>() >= size_of::<TypeId>(),
* add missing check in case Device::drvdata() is called from probe().
- Danilo ]
> rust: auxiliary: consider auxiliary devices always have a parent
> rust: auxiliary: unregister on parent device unbind
> rust: auxiliary: move parent() to impl Device
> rust: auxiliary: implement parent() for Device<Bound>
> samples: rust: auxiliary: misc cleanup of ParentDriver::connect()
> samples: rust: auxiliary: illustrate driver interaction
Powered by blists - more mailing lists