[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <DF4J31QHOZ9K.2I58JYI6FBJHA@kernel.org>
Date: Mon, 22 Dec 2025 07:23:26 +0100
From: "Benno Lossin" <lossin@...nel.org>
To: "Lyude Paul" <lyude@...hat.com>, <rust-for-linux@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, "Thomas Gleixner" <tglx@...utronix.de>
Cc: "Boqun Feng" <boqun.feng@...il.com>, "Daniel Almeida"
<daniel.almeida@...labora.com>, "Miguel Ojeda" <ojeda@...nel.org>, "Alex
Gaynor" <alex.gaynor@...il.com>, "Gary Guo" <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>, "Andreas
Hindborg" <a.hindborg@...nel.org>, "Alice Ryhl" <aliceryhl@...gle.com>,
"Trevor Gross" <tmgross@...ch.edu>, "Danilo Krummrich" <dakr@...nel.org>,
"Andrew Morton" <akpm@...ux-foundation.org>, "Peter Zijlstra"
<peterz@...radead.org>, "Ingo Molnar" <mingo@...hat.com>, "Will Deacon"
<will@...nel.org>, "Waiman Long" <longman@...hat.com>
Subject: Re: [PATCH v16 12/17] rust: sync: lock/global: Rename B to G in
trait bounds
On Mon Dec 15, 2025 at 6:57 PM CET, Lyude Paul wrote:
> Due to the introduction of Backend::BackendInContext, if we want to be able
> support Lock types with a Context we need to be able to handle the fact
> that the Backend for a returned Guard may not exactly match the Backend for
> the lock. Before we add this though, rename B to G in all of our trait
> bounds to make sure things don't become more difficult to understand once
> we add a Backend bound.
Would be better to have this patch directly before the patch that needs
this.
Reviewed-by: Benno Lossin <lossin@...nel.org>
Cheers,
Benno
>
> There should be no functional changes in this patch.
>
> Signed-off-by: Lyude Paul <lyude@...hat.com>
Powered by blists - more mailing lists