From: Boqun Feng <boqun.feng@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "Tamir Duberstein" <tamird@kernel.org>,
"Miguel Ojeda" <ojeda@kernel.org>, "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>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL][PATCH 0/1] Fixes for Rust synchronization PR of v7.0
Date: Mon, 26 Jan 2026 22:12:53 -0800 [thread overview]
Message-ID: <aXhXZdkBAwHukksg@tardis.local> (raw)
In-Reply-To: <20260123054624.8226-1-boqun.feng@gmail.com>
On Thu, Jan 22, 2026 at 09:46:23PM -0800, Boqun Feng wrote:
> Hi Peter,
>
Gentle ping ;-)
Thanks!
Regards,
Boqun
> 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!()
> -----BEGIN PGP SIGNATURE-----
>
> iQFJBAABCAAzFiEEj5IosQTPz8XU1wRHSXnow7UH+rgFAmlzCUwVHGJvcXVuLmZl
> bmdAZ21haWwuY29tAAoJEEl56MO1B/q43YYIAIkVv+YTbNpODC5Kfy2F0/XxeHoB
> MbBSKvma6QR2m1Qx0c09o2NKcEU4ZnoPEi4WDhAs1ftfSyyc1CwE6gBApFirBvIu
> VzAWcEKJkM16+IiWQDQKPbWssraNmKGw4zeZlXi6q+iry+2r+Hy+6JdikcgCshYn
> +BYKjrkAh+mkXrQ1F95PfK0tfiT8fIbJCIeroPi9HlCmNlAYx0dP0i3YvF+5nWhB
> a5rU4TmQDKmCXXwyIqVQeOkK4kMme6wPOOSxjd5g4W/srS9hcmM3mYAASl1omm2X
> hr/9yyUOxSLUkG9e0x9XIhBkK4YwGS0dLIG6SQCvh//2vX9ek8BzBUvHzE0=
> =xOu4
> -----END PGP SIGNATURE-----
>
> ----------------------------------------------------------------
> Tamir Duberstein (1):
> rust: sync: Replace `kernel::c_str!` with C-Strings
>
> rust/kernel/sync.rs | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> --
> 2.50.1 (Apple Git-155)
>
next prev parent reply other threads:[~2026-01-27 6:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 21:13 [PATCH] rust: sync: replace `kernel::c_str!` with C-Strings Tamir Duberstein
2026-01-20 21:16 ` Gary Guo
2026-01-21 1:09 ` Boqun Feng
2026-01-23 5:46 ` [GIT PULL][PATCH 0/1] Fixes for Rust synchronization PR of v7.0 Boqun Feng
2026-01-23 5:46 ` [PATCH 1/1] rust: sync: Replace `kernel::c_str!` with C-Strings Boqun Feng
2026-01-27 6:12 ` Boqun Feng [this message]
2026-01-27 8:30 ` [GIT PULL][PATCH 0/1] Fixes for Rust synchronization PR of v7.0 Peter Zijlstra
2026-01-27 14:06 ` Boqun Feng
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=aXhXZdkBAwHukksg@tardis.local \
--to=boqun.feng@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=peterz@infradead.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tamird@kernel.org \
--cc=tmgross@umich.edu \
/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