mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Gary Guo" <gary@garyguo.net>
To: "Ryan Foster" <foster.ryan.r@gmail.com>, <gary@garyguo.net>
Cc: <a.hindborg@kernel.org>, <aliceryhl@google.com>,
	<bjorn3_gh@protonmail.com>, <boqun.feng@gmail.com>,
	<dakr@kernel.org>, <gregkh@linuxfoundation.org>,
	<linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<lossin@kernel.org>, <ojeda@kernel.org>, <rafael@kernel.org>,
	<rust-for-linux@vger.kernel.org>, <tmgross@umich.edu>
Subject: Re: [PATCH] rust: replace `kernel::c_str!` with C-Strings in seq_file and device
Date: Tue, 20 Jan 2026 15:02:26 +0000	[thread overview]
Message-ID: <DFTIA7Y3MZFR.3LEHVWENE4Q4R@garyguo.net> (raw)
In-Reply-To: <20260120145912.281977-1-foster.ryan.r@gmail.com>

On Tue Jan 20, 2026 at 2:59 PM GMT, Ryan Foster wrote:
> C-String literals were added in Rust 1.77. Replace instances of
> `kernel::c_str!` with C-String literals where possible.
> 
> This patch updates seq_file and device modules to use the native
> C-string literal syntax (c"...") instead of the kernel::c_str! macro.
> 
> While at it, convert imports to the kernel vertical import style.
> 
> Signed-off-by: Ryan Foster <foster.ryan.r@gmail.com>

Reviewed-by: Gary Guo <gary@garyguo.net>

> ---
>  rust/kernel/device.rs   | 19 ++++++++++++-------
>  rust/kernel/seq_file.rs | 12 ++++++++++--
>  2 files changed, 22 insertions(+), 9 deletions(-)


  reply	other threads:[~2026-01-20 15:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-20 14:02 Ryan Foster
2026-01-20 14:49 ` Gary Guo
2026-01-20 14:59   ` Ryan Foster
2026-01-20 15:02     ` Gary Guo [this message]
2026-01-20 21:11       ` Tamir Duberstein
2026-01-20 15:00   ` ryan foster

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=DFTIA7Y3MZFR.3LEHVWENE4Q4R@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=foster.ryan.r@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lossin@kernel.org \
    --cc=ojeda@kernel.org \
    --cc=rafael@kernel.org \
    --cc=rust-for-linux@vger.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®