[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aWinBMASjagM8gNQ@tardis-2.local>
Date: Thu, 15 Jan 2026 16:40:35 +0800
From: Boqun Feng <boqun.feng@...il.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
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>, Gary Guo <gary@...yguo.net>,
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>,
Viresh Kumar <viresh.kumar@...aro.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 5/7] rust: sync: refcount: always inline functions
using build_assert with arguments
On Thu, Jan 15, 2026 at 08:49:05AM +0100, Miguel Ojeda wrote:
> On Mon, Dec 8, 2025 at 3:47 AM Alexandre Courbot <acourbot@...dia.com> wrote:
> >
> > `build_assert` relies on the compiler to optimize out its error path.
> > Functions using it with its arguments must thus always be inlined,
> > otherwise the error path of `build_assert` might not be optimized out,
> > triggering a build error.
> >
> > Cc: stable@...r.kernel.org
> > Fixes: bb38f35b35f9 ("rust: implement `kernel::sync::Refcount`")
> > Reviewed-by: Daniel Almeida <daniel.almeida@...labora.com>
> > Signed-off-by: Alexandre Courbot <acourbot@...dia.com>
>
> Boqun et al.: do you want to pick this one or should I take it with
> your Acked-by?
>
Acked-by: Boqun Feng <boqun.feng@...il.com>
Going via rust-next seems more appropriate to me, thanks!
Regards,
Boqun
> Thanks!
>
> Cheers,
> Miguel
Powered by blists - more mailing lists