Re: [GIT PULL][PATCH 0/1] Fixes for Rust synchronization PR of v7.0

From: Boqun Feng

Date: Tue Jan 27 2026 - 09:07:08 EST


On Tue, Jan 27, 2026 at 09:30:14AM +0100, Peter Zijlstra wrote:
> 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

No, it's targeting tip/locking/core, it's a fix to the PR that is going
into v7.0. Or I guess I could just say it's a "part 2" for the PR to
reduce ambiguity?

Regards,
Boqun

> doesn't apply :/