[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <xhpapgzctldhwhjdaomu252vqyrljwunc4gis6neuap4x3nppp@rqbrauohopgv>
Date: Tue, 16 Dec 2025 12:18:08 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Gary Guo <gary@...yguo.net>
Cc: Alexandre Courbot <acourbot@...dia.com>,
Danilo Krummrich <dakr@...nel.org>, Alice Ryhl <aliceryhl@...gle.com>,
Daniel Almeida <daniel.almeida@...labora.com>, Miguel Ojeda <ojeda@...nel.org>,
Alex Gaynor <alex.gaynor@...il.com>, Boqun Feng <boqun.feng@...il.com>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>, Benno Lossin <lossin@...nel.org>,
Andreas Hindborg <a.hindborg@...nel.org>, Trevor Gross <tmgross@...ch.edu>,
"Rafael J. Wysocki" <rafael@...nel.org>, Will Deacon <will@...nel.org>,
Peter Zijlstra <peterz@...radead.org>, Mark Rutland <mark.rutland@....com>,
rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org,
stable@...r.kernel.org
Subject: Re: [PATCH v3 3/7] rust: cpufreq: always inline functions using
build_assert with arguments
On 15-12-25, 11:14, Gary Guo wrote:
> Thinking again about this I think `#[inline(always)]` is fine to keep as
> it can also be used to indicate "this function shall never be codegenned".
>
> However I do still think the comment is confusing per-se as there is no
> "optimization" for this function at all.
>
> RE: the patch I am fine either without this patch picked or having this
> patch in and fix the comment later.
Thanks Gary. I will keep the patch then and apply add-ons later.
--
viresh
Powered by blists - more mailing lists