[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID:
<BL0PR02MB491496C88E898872E92339E2E9562@BL0PR02MB4914.namprd02.prod.outlook.com>
Date: Fri, 1 Nov 2024 10:23:23 +0000
From: Filipe Xavier <felipe_life@...e.com>
To: Lyude Paul <lyude@...hat.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"rust-for-linux@...r.kernel.org" <rust-for-linux@...r.kernel.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
<benno.lossin@...ton.me>, Andreas Hindborg <a.hindborg@...nel.org>, Alice
Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>, Martin
Rodriguez Reboredo <yakoyoku@...il.com>, Valentin Obst
<kernel@...entinobst.de>
Subject: Re: [PATCH v3 2/2] rust: sync: Make Guard::new() public
On Fri, Nov 1, 2024 at 12:10 AM Lyude Paul <lyude@...hat.com> wrote:
>
> Since we added a Lock::from_raw() function previously, it makes sense to
> also introduce an interface for creating a Guard from a reference to a Lock
> for instances where we've derived the Lock from a raw pointer and know that
> the lock is already acquired, something we do in the KMS API.
>
> Signed-off-by: Lyude Paul <lyude@...hat.com>
Reviewed-by: Filipe Xavier <felipe_life@...e.com>
Powered by blists - more mailing lists