From: "Gary Guo" <gary@garyguo.net>
To: "Tamir Duberstein" <tamird@kernel.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun.feng@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>
Cc: <rust-for-linux@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] rust: sync: replace `kernel::c_str!` with C-Strings
Date: Tue, 20 Jan 2026 21:16:20 +0000 [thread overview]
Message-ID: <DFTQ8I30EH0A.H7A68JG8VBXZ@garyguo.net> (raw)
In-Reply-To: <20260120-cstr-sync-again-v1-1-2a775a2a36fd@kernel.org>
On Tue Jan 20, 2026 at 9:13 PM GMT, Tamir Duberstein wrote:
> C-String literals were added in Rust 1.77. Replace instances of
> `kernel::c_str!` with C-String literals where possible.
>
> Signed-off-by: Tamir Duberstein <tamird@kernel.org>
Reviewed-by: Gary Guo <gary@garyguo.net>
> ---
> This is the same as my earlier change[0] but applies to additional
> code[1] which didn't make it to mainline in a timely manner and is now
> queued for v7.0.
>
> Link: https://lore.kernel.org/all/20251117-core-cstr-cstrings-v4-1-924886ad9f75@gmail.com/ [0]
> Link: https://lore.kernel.org/all/20250811-lock-class-key-cleanup-v3-2-b12967ee1ca2@google.com/ [1]
> ---
> rust/kernel/sync.rs | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
next prev parent reply other threads:[~2026-01-20 21:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 21:13 Tamir Duberstein
2026-01-20 21:16 ` Gary Guo [this message]
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-28 8:33 ` [tip: locking/core] " tip-bot2 for Tamir Duberstein
2026-01-27 6:12 ` [GIT PULL][PATCH 0/1] Fixes for Rust synchronization PR of v7.0 Boqun Feng
2026-01-27 8:30 ` 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=DFTQ8I30EH0A.H7A68JG8VBXZ@garyguo.net \
--to=gary@garyguo.net \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.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
all inboxes | Powered by JetHome®