[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250619075925.b2s4ngza75kc3dsj@vireshk-i7>
Date: Thu, 19 Jun 2025 13:29:25 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
Cc: Abhinav Ananthu <abhinav.ogl@...il.com>,
"Rafael J . Wysocki" <rafael@...nel.org>,
Miguel Ojeda <ojeda@...nel.org>,
Alex Gaynor <alex.gaynor@...il.com>,
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>, linux-pm@...r.kernel.org,
rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] rust: cpufreq: Ensure C ABI compatibility in all
unsafe
On 19-06-25, 09:32, Miguel Ojeda wrote:
> In any case, from now on, one should just refer to them directly as
> `c_*` (please use the `kernel` prelude for that) -- please see:
>
> https://docs.kernel.org/rust/coding-guidelines.html#c-ffi-types
>
> I hope that helps!
Thanks.
--
viresh
Powered by blists - more mailing lists