[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAH5fLgh=qgJ-+VzzVn=jGTJUQDx6WSiUaRLYouQknuKkCi05dw@mail.gmail.com>
Date: Fri, 1 Nov 2024 10:11:11 +0100
From: Alice Ryhl <aliceryhl@...gle.com>
To: Lyude Paul <lyude@...hat.com>
Cc: rust-for-linux@...r.kernel.org, linux-kernel@...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>,
Trevor Gross <tmgross@...ch.edu>, Martin Rodriguez Reboredo <yakoyoku@...il.com>,
Valentin Obst <kernel@...entinobst.de>, Filipe Xavier <felipe_life@...e.com>
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: Alice Ryhl <aliceryhl@...gle.com>
Powered by blists - more mailing lists