[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250620094330.m3batzq7oknwk4lz@vireshk-i7>
Date: Fri, 20 Jun 2025 15:13:30 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Abhinav Ananthu <abhinav.ogl@...il.com>
Cc: rafael@...nel.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, aliceryhl@...gle.com,
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 20-06-25, 14:22, Abhinav Ananthu 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>
> ---
> rust/kernel/cpufreq.rs | 30 +++++++++++++++---------------
> 1 file changed, 15 insertions(+), 15 deletions(-)
Applied. Thanks.
--
viresh
Powered by blists - more mailing lists