[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <D96AR6IOMJ0I.1YH5KT3QX2YHF@proton.me>
Date: Mon, 14 Apr 2025 10:41:23 +0000
From: Benno Lossin <benno.lossin@...ton.me>
To: Danilo Krummrich <dakr@...nel.org>, bhelgaas@...gle.com, kwilczynski@...nel.org, gregkh@...uxfoundation.org, rafael@...nel.org, abdiel.janulgue@...il.com
Cc: ojeda@...nel.org, alex.gaynor@...il.com, boqun.feng@...il.com, gary@...yguo.net, bjorn3_gh@...tonmail.com, a.hindborg@...nel.org, aliceryhl@...gle.com, tmgross@...ch.edu, daniel.almeida@...labora.com, robin.murphy@....com, linux-pci@...r.kernel.org, rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/9] rust: device: implement impl_device_context_deref!
On Sun Apr 13, 2025 at 7:36 PM CEST, Danilo Krummrich wrote:
> +/// Implement [`core::ops::Deref`] traits for allowed [`DeviceContext`] conversions of a (bus
> +/// specific) device.
> +///
> +/// # Safety
> +///
> +/// The type given as `$device` must be a transparent wrapper of a type that doesn't depend on the
> +/// generic argument of `$device`.
> +#[macro_export]
> +macro_rules! impl_device_context_deref {
> + (unsafe { $device:ident }) => {
> + // SAFETY: This macro has the exact same safety requirement as
> + // `__impl_device_context_deref!`.
> + kernel::__impl_device_context_deref!(unsafe {
Missing `::` in front of `kernel`.
---
Cheers,
Benno
> + $device,
> + $crate::device::Core => $crate::device::Normal
> + });
> + };
> +}
> +
> #[doc(hidden)]
> #[macro_export]
> macro_rules! dev_printk {
Powered by blists - more mailing lists