[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3aa3ef74-ee40-4a57-94c8-bf642e23aee5@foxido.dev>
Date: Tue, 23 Dec 2025 19:36:34 +0300
From: Gladyshev Ilya <foxido@...ido.dev>
To: "Rafael J. Wysocki" <rafael@...nel.org>
Cc: Len Brown <lenb@...nel.org>, Miguel Ojeda <ojeda@...nel.org>,
Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <lossin@...nel.org>, Andreas Hindborg <a.hindborg@...nel.org>,
Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>,
Danilo Krummrich <dakr@...nel.org>, Tamir Duberstein <tamird@...il.com>,
Armin Wolf <W_Armin@....de>, platform-driver-x86@...r.kernel.org,
linux-kernel@...r.kernel.org, rust-for-linux@...r.kernel.org,
linux-acpi@...r.kernel.org
Subject: Re: [RFC PATCH 1/3] rust: implement wrapper for acpi_object
On 12/22/25 22:32, Rafael J. Wysocki wrote:
> On Sun, Dec 21, 2025 at 7:24 PM Gladyshev Ilya <foxido@...ido.dev> wrote:
>>
>> ACPI Object is represented via union on C-side. On Rust side, it's
>> zero-cost type wrapper for each ACPI Type, with individual methods for
>> getters and other interactions.
>
> This is ACPICA stuff though and switching over ACPICA to Rust any time
> soon is rather unlikely.
>
> Is this really needed on the Rust side?
At least acpi_buffer is needed, and for now, only that will be wrapped
(I will remove other types).
Note that there are no actual types on the Rust side, only transparent
wrappers around C acpi structs (for type safety).
Powered by blists - more mailing lists