[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250108053705.cuog2jqj4x2oa5im@vireshk-i7>
Date: Wed, 8 Jan 2025 11:07:05 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>,
Miguel Ojeda <miguel.ojeda.sandonis@...il.com>,
Danilo Krummrich <dakr@...hat.com>, 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 <benno.lossin@...ton.me>,
Andreas Hindborg <a.hindborg@...nel.org>,
Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>,
linux-pm@...r.kernel.org,
Vincent Guittot <vincent.guittot@...aro.org>,
Stephen Boyd <sboyd@...nel.org>, Nishanth Menon <nm@...com>,
rust-for-linux@...r.kernel.org,
Manos Pitsidianakis <manos.pitsidianakis@...aro.org>,
Erik Schilling <erik.schilling@...aro.org>,
Alex Bennée <alex.bennee@...aro.org>,
Joakim Bech <joakim.bech@...aro.org>, Rob Herring <robh@...nel.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH V6 03/15] cpufreq: Rust implementation doesn't parse
BIT() macro
On 07-01-25, 13:00, Greg KH wrote:
> On Tue, Jan 07, 2025 at 04:51:36PM +0530, Viresh Kumar wrote:
> > Rust isn't able to parse the macro for now, avoid using it.
>
> No, please fix it. You don't want to have to fend off the checkpatch.pl
> cleanups that this would cause of people putting the BIT() macro back.
Yeah, I mentioned this in the cover-letter that we need to make Rust work with
it. I should have marked it as DO-NOT-MERGE patch.
I wanted to get an idea from others on how to fix it, which Danilo shared now.
Will try that.
> Make BIT() work properly for Rust code as well, it has to be done
> eventually, right?
--
viresh
Powered by blists - more mailing lists