From: Benno Lossin <benno.lossin@proton.me>
To: Danilo Krummrich <dakr@kernel.org>,
bhelgaas@google.com, gregkh@linuxfoundation.org,
rafael@kernel.org, ojeda@kernel.org, alex.gaynor@gmail.com,
boqun.feng@gmail.com, gary@garyguo.net, bjorn3_gh@protonmail.com,
a.hindborg@kernel.org, aliceryhl@google.com, tmgross@umich.edu
Cc: linux-pci@vger.kernel.org, rust-for-linux@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/4] rust: platform: impl TryFrom<&Device> for &platform::Device
Date: Thu, 20 Mar 2025 23:44:31 +0000 [thread overview]
Message-ID: <D8LHR6S7X0XT.32HULT1QFYKUX@proton.me> (raw)
In-Reply-To: <20250320222823.16509-5-dakr@kernel.org>
On Thu Mar 20, 2025 at 11:27 PM CET, Danilo Krummrich wrote:
> @@ -234,6 +234,24 @@ fn as_ref(&self) -> &device::Device {
> }
> }
>
> +impl TryFrom<&device::Device> for &Device {
> + type Error = kernel::error::Error;
> +
> + fn try_from(dev: &device::Device) -> Result<Self, Self::Error> {
> + if dev.bus_type_raw() != addr_of!(bindings::platform_bus_type) {
> + return Err(EINVAL);
> + }
> +
> + // SAFETY: We've just verified that the bus type of `dev` equals
> + // `bindings::platform_bus_type`, hence `dev` must be embedded in a valid
> + // `struct platform_device`.
Same change here as in patch 3. With that:
Reviewed-by: Benno Lossin <benno.lossin@proton.me>
---
Cheers,
Benno
> + let pdev = unsafe { container_of!(dev.as_raw(), bindings::platform_device, dev) };
> +
> + // SAFETY: `pdev` is a valid pointer to a `struct platform_device`.
> + Ok(unsafe { &*pdev.cast() })
> + }
> +}
> +
> // SAFETY: A `Device` is always reference-counted and can be released from any thread.
> unsafe impl Send for Device {}
>
prev parent reply other threads:[~2025-03-20 23:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 22:27 [PATCH v2 0/4] Implement TryFrom<&Device> for bus specific devices Danilo Krummrich
2025-03-20 22:27 ` [PATCH v2 1/4] rust: device: implement Device::parent() Danilo Krummrich
2025-03-20 22:44 ` Benno Lossin
2025-03-20 23:46 ` Danilo Krummrich
2025-03-21 1:40 ` Greg KH
2025-03-21 9:04 ` Danilo Krummrich
2025-03-21 13:03 ` Danilo Krummrich
2025-03-21 13:09 ` Greg KH
2025-03-21 14:16 ` Danilo Krummrich
2025-03-21 14:40 ` Boqun Feng
2025-03-21 14:46 ` Danilo Krummrich
2025-03-20 22:27 ` [PATCH v2 2/4] rust: device: implement bus_type_raw() Danilo Krummrich
2025-03-20 22:55 ` Benno Lossin
2025-03-20 22:27 ` [PATCH v2 3/4] rust: pci: impl TryFrom<&Device> for &pci::Device Danilo Krummrich
2025-03-20 23:44 ` Benno Lossin
2025-03-20 23:48 ` Danilo Krummrich
2025-03-21 16:56 ` kernel test robot
2025-03-21 17:44 ` Danilo Krummrich
2025-03-21 18:59 ` Miguel Ojeda
2025-03-21 19:11 ` Danilo Krummrich
2025-03-21 19:37 ` Miguel Ojeda
2025-03-22 10:08 ` Benno Lossin
2025-03-20 22:27 ` [PATCH v2 4/4] rust: platform: impl TryFrom<&Device> for &platform::Device Danilo Krummrich
2025-03-20 23:44 ` Benno Lossin [this message]
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=D8LHR6S7X0XT.32HULT1QFYKUX@proton.me \
--to=benno.lossin@proton.me \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bhelgaas@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rafael@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;
as well as URLs for NNTP newsgroup(s).