From: Dirk Behme <dirk.behme@gmail.com>
To: Lyude Paul <lyude@redhat.com>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Cc: "Boqun Feng" <boqun.feng@gmail.com>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Peter Zijlstra" <peterz@infradead.org>,
"Ingo Molnar" <mingo@redhat.com>, "Will Deacon" <will@kernel.org>,
"Waiman Long" <longman@redhat.com>
Subject: Re: [PATCH v16 12/17] rust: sync: lock/global: Rename B to G in trait bounds
Date: Tue, 16 Dec 2025 17:15:18 +0100 [thread overview]
Message-ID: <08d00540-9de9-43a5-9e36-df2d575b4c24@gmail.com> (raw)
In-Reply-To: <20251215175806.102713-13-lyude@redhat.com>
On 15.12.25 18:57, 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.
>
> There should be no functional changes in this patch.
>
> Signed-off-by: Lyude Paul <lyude@redhat.com>
> ---
> rust/kernel/sync/atomic.rs | 2 +-
> rust/kernel/sync/lock/global.rs | 58 ++++++++++++++++-----------------
> 2 files changed, 30 insertions(+), 30 deletions(-)
>
> diff --git a/rust/kernel/sync/atomic.rs b/rust/kernel/sync/atomic.rs
> index 3afc376be42d9..c07a53f8360b4 100644
> --- a/rust/kernel/sync/atomic.rs
> +++ b/rust/kernel/sync/atomic.rs
> @@ -21,8 +21,8 @@
> mod predefine;
>
> pub use internal::AtomicImpl;
> -pub use ordering::{Acquire, Full, Relaxed, Release};
> pub(crate) use internal::{AtomicArithmeticOps, AtomicBasicOps, AtomicExchangeOps};
> +pub use ordering::{Acquire, Full, Relaxed, Release};
Just fyi, there is a (trivial) conflict of this with Miguel's recently
merged
commit 309e49039f124a ("rust: sync: atomic: separate import "blocks"")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/rust/kernel/sync/atomic.rs?id=309e49039f124a9dcb99c05651af8eb8fa05bc29
If I haven't missed anything this is just to fix the alphabetical
order? So maybe this should go as an independent patch like Miguel's one?
Dirk
next prev parent reply other threads:[~2025-12-16 16:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 17:57 [PATCH v16 00/17] Refcounted interrupts, SpinLockIrq for rust Lyude Paul
2025-12-15 17:57 ` [PATCH v16 01/17] preempt: Introduce HARDIRQ_DISABLE_BITS Lyude Paul
2025-12-15 17:57 ` [PATCH v16 02/17] preempt: Track NMI nesting to separate per-CPU counter Lyude Paul
2025-12-15 17:57 ` [PATCH v16 03/17] preempt: Introduce __preempt_count_{sub, add}_return() Lyude Paul
2025-12-15 17:57 ` [PATCH v16 04/17] openrisc: Include <linux/cpumask.h> in smp.h Lyude Paul
2025-12-15 21:54 ` Stafford Horne
2025-12-15 17:57 ` [PATCH v16 05/17] irq & spin_lock: Add counted interrupt disabling/enabling Lyude Paul
2025-12-15 17:57 ` [PATCH v16 06/17] irq: Add KUnit test for refcounted interrupt enable/disable Lyude Paul
2025-12-15 17:57 ` [PATCH v16 07/17] rust: Introduce interrupt module Lyude Paul
2025-12-15 17:57 ` [PATCH v16 08/17] rust: helper: Add spin_{un,}lock_irq_{enable,disable}() helpers Lyude Paul
2025-12-16 12:15 ` Gary Guo
2025-12-15 17:57 ` [PATCH v16 09/17] rust: sync: Add SpinLockIrq Lyude Paul
2025-12-16 12:20 ` Gary Guo
2025-12-15 17:57 ` [PATCH v16 10/17] rust: sync: Introduce lock::Backend::Context Lyude Paul
2025-12-15 17:57 ` [PATCH v16 11/17] rust: sync: lock: Add `Backend::BackendInContext` Lyude Paul
2025-12-15 17:57 ` [PATCH v16 12/17] rust: sync: lock/global: Rename B to G in trait bounds Lyude Paul
2025-12-16 16:15 ` Dirk Behme [this message]
2025-12-17 20:33 ` Boqun Feng
2025-12-15 17:58 ` [PATCH v16 13/17] rust: sync: Add a lifetime parameter to lock::global::GlobalGuard Lyude Paul
2025-12-15 17:58 ` [PATCH v16 14/17] rust: sync: Expose lock::Backend Lyude Paul
2025-12-15 17:58 ` [PATCH v16 15/17] rust: sync: lock/global: Add Backend parameter to GlobalGuard Lyude Paul
2025-12-15 17:58 ` [PATCH v16 16/17] rust: sync: lock/global: Add BackendInContext support to GlobalLock Lyude Paul
2025-12-15 17:58 ` [PATCH v16 17/17] locking: Switch to _irq_{disable,enable}() variants in cleanup guards Lyude Paul
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=08d00540-9de9-43a5-9e36-df2d575b4c24@gmail.com \
--to=dirk.behme@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=lossin@kernel.org \
--cc=lyude@redhat.com \
--cc=mingo@redhat.com \
--cc=ojeda@kernel.org \
--cc=peterz@infradead.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tmgross@umich.edu \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).