[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251013155205.2004838-15-lyude@redhat.com>
Date: Mon, 13 Oct 2025 11:48:16 -0400
From: Lyude Paul <lyude@...hat.com>
To: rust-for-linux@...r.kernel.org,
Thomas Gleixner <tglx@...utronix.de>,
Boqun Feng <boqun.feng@...il.com>,
linux-kernel@...r.kernel.org,
Daniel Almeida <daniel.almeida@...labora.com>
Cc: Miguel Ojeda <ojeda@...nel.org>,
Alex Gaynor <alex.gaynor@...il.com>,
Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <lossin@...nel.org>,
Andreas Hindborg <a.hindborg@...nel.org>,
Alice Ryhl <aliceryhl@...gle.com>,
Trevor Gross <tmgross@...ch.edu>,
Danilo Krummrich <dakr@...nel.org>,
Mitchell Levy <levymitchell0@...il.com>,
Shankari Anand <shankari.ak0208@...il.com>
Subject: [PATCH v13 14/17] rust: sync: Expose lock::Backend
Due to the addition of sync::lock::Backend::Context, lock guards can be
returned with a different Backend than their respective lock. Since we'll
be adding a trait bound for Backend to GlobalGuard in order to support
this, users will need to be able to directly refer to Backend so that they
can use it in trait bounds.
So, let's make this easier for users and expose Backend in sync.
Signed-off-by: Lyude Paul <lyude@...hat.com>
---
rust/kernel/sync.rs | 1 +
1 file changed, 1 insertion(+)
diff --git a/rust/kernel/sync.rs b/rust/kernel/sync.rs
index f293bbe13e855..795cbf3fc10f7 100644
--- a/rust/kernel/sync.rs
+++ b/rust/kernel/sync.rs
@@ -29,6 +29,7 @@
pub use lock::spinlock::{
new_spinlock, new_spinlock_irq, SpinLock, SpinLockGuard, SpinLockIrq, SpinLockIrqGuard,
};
+pub use lock::Backend;
pub use locked_by::LockedBy;
pub use refcount::Refcount;
--
2.51.0
Powered by blists - more mailing lists