[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aEVpL8wIfGDZRyUN@pollux>
Date: Sun, 8 Jun 2025 12:42:55 +0200
From: Danilo Krummrich <dakr@...nel.org>
To: Benno Lossin <lossin@...nel.org>
Cc: Igor Korotin <igor.korotin.linux@...il.com>, ojeda@...nel.org,
alex.gaynor@...il.com, rafael@...nel.org,
gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org,
rust-for-linux@...r.kernel.org, linux-acpi@...r.kernel.org,
boqun.feng@...il.com, gary@...yguo.net, bjorn3_gh@...tonmail.com,
benno.lossin@...ton.me, a.hindborg@...nel.org, aliceryhl@...gle.com,
tmgross@...ch.edu, lenb@...nel.org, wedsonaf@...il.com,
viresh.kumar@...aro.org, alex.hung@....com,
dingxiangfei2009@...il.com
Subject: Re: [PATCH v3 1/4] rust: acpi: add `acpi::DeviceId` abstraction
On Sun, Jun 08, 2025 at 09:48:00AM +0200, Benno Lossin wrote:
> On Fri Jun 6, 2025 at 7:06 PM CEST, Igor Korotin wrote:
> > +impl DeviceId {
> > + const ACPI_ID_LEN: usize = 16;
> > +
> > + /// Create a new device id from an ACPI 'id' string.
> > + pub const fn new(id: &'static CStr) -> Self {
> > + assert!(id.len() <= Self::ACPI_ID_LEN, "ID exceeds 16 bytes");
> > + let src = id.as_bytes_with_nul();
> > + // Replace with `bindings::acpi_device_id::default()` once stabilized for `const`.
> > + // SAFETY: FFI type is valid to be zero-initialized.
> > + let mut acpi: bindings::acpi_device_id = unsafe { core::mem::zeroed() };
>
> This can be made safe using this series:
>
> https://lore.kernel.org/all/20250523145125.523275-1-lossin@kernel.org
Indeed, I did not mention this though since I think this series should not
depend on the one above. They'll land through different trees and the
improvement can still be made later on.
Powered by blists - more mailing lists