[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260127083014.GT171111@noisy.programming.kicks-ass.net>
Date: Tue, 27 Jan 2026 09:30:14 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Boqun Feng <boqun.feng@...il.com>
Cc: Tamir Duberstein <tamird@...nel.org>, Miguel Ojeda <ojeda@...nel.org>,
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>, rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL][PATCH 0/1] Fixes for Rust synchronization PR of v7.0
On Thu, Jan 22, 2026 at 09:46:23PM -0800, Boqun Feng wrote:
> Hi Peter,
>
> Although we chatted about this over IRC, but I figured it might be
> better for me to just send a fix PR for this, so here is it.
>
> Thanks!
>
> Regards,
> Boqun
>
> --------------------------------->8
> The following changes since commit ccf9e070116a81d29aae30db501d562c8efd1ed8:
>
> rust: sync: Inline various lock related methods (2026-01-10 10:53:46 +0800)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/boqun/linux.git tags/rust-sync-fixes-for-v7.0-pr
>
> for you to fetch changes up to 6583920e15fc567109e1c64ca58c917f52f40736:
>
> rust: sync: Replace `kernel::c_str!` with C-Strings (2026-01-22 21:36:57 -0800)
>
> ----------------------------------------------------------------
> Fixes for Rust sync v7.0 PR:
>
> - Remove the usage of `c_str!()` in the example of static_lock_class!()
So I'm notoriously bad at keeping track of version numbers; but I'm
thinking you want this in tip/locking/urgent, right? Thing is, it
doesn't apply :/
Powered by blists - more mailing lists