[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAH5fLgi-QG2KRt6mAiU3P-tyVG_xevPzB6VK_W=is2B+7=63kQ@mail.gmail.com>
Date: Fri, 20 Jun 2025 11:20:08 +0200
From: Alice Ryhl <aliceryhl@...gle.com>
To: Abhinav Ananthu <abhinav.ogl@...il.com>
Cc: rafael@...nel.org, viresh.kumar@...aro.org, 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,
tmgross@...ch.edu, dakr@...nel.org, linux-pm@...r.kernel.org,
rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] rust: cpufreq: use c_ types from kernel prelude
On Fri, Jun 20, 2025 at 10:55 AM Abhinav Ananthu <abhinav.ogl@...il.com> wrote:
>
> Update cpufreq FFI callback signatures to use `c_int` from the `kernel::prelude`,
> rather than accessing it explicitly through `kernel::ffi::c_int`.
>
> Although these types are defined in the `ffi` crate, they are re-exported
> via `kernel::prelude`. This aligns with the Rust-for-Linux coding
> guidelines and ensures proper C ABI compatibility across platforms.
>
> Signed-off-by: Abhinav Ananthu <abhinav.ogl@...il.com>
> Suggested-by: Viresh Kumar <viresh.kumar@...aro.org>
Reviewed-by: Alice Ryhl <aliceryhl@...gle.com>
Powered by blists - more mailing lists