From: David Gow <david@davidgow.net>
To: "Alexandre Courbot" <acourbot@nvidia.com>,
"Brendan Higgins" <brendan.higgins@linux.dev>,
"Rae Moar" <raemoar63@gmail.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun@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>,
"Shuah Khan" <skhan@linuxfoundation.org>
Cc: linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rust: kunit: fix warning when !CONFIG_PRINTK
Date: Tue, 24 Feb 2026 17:01:10 +0800 [thread overview]
Message-ID: <b963ea9b-69d5-4d4e-8c1d-8e969c545a79@davidgow.net> (raw)
In-Reply-To: <20260224-unused_var_err-v1-1-c51d805eceb5@nvidia.com>
Le 24/02/2026 à 3:45 PM, 'Alexandre Courbot' via KUnit Development a écrit :
> If `CONFIG_PRINTK` is not set, then the following warnings are issued
> during build:
>
> warning: unused variable: `args`
> --> ../rust/kernel/kunit.rs:16:12
> |
> 16 | pub fn err(args: fmt::Arguments<'_>) {
> | ^^^^ help: if this is intentional, prefix it with an underscore: `_args`
> |
> = note: `#[warn(unused_variables)]` (part of `#[warn(unused)]`) on by default
>
> warning: unused variable: `args`
> --> ../rust/kernel/kunit.rs:32:13
> |
> 32 | pub fn info(args: fmt::Arguments<'_>) {
> | ^^^^ help: if this is intentional, prefix it with an underscore: `_args`
>
> Fix this by allowing unused variables on these methods for this
> (arguably rare) case.
>
> Fixes: a66d733da801 ("rust: support running Rust documentation tests as KUnit ones")
> Signed-off-by: Alexandre Courbot <acourbot@nvidia.com>
> ---
Thanks. I think Alice's suggestion of adding a `let _ = args;` line,
rather than disabling the unused_variables warning is probably the
better way of handling this.
(That being said, those err() and info() functions probably need some
reworking so that -- in the cases where it makes sense -- they call into
the KUnit logging functions, not just printk.)
Cheers,
-- David
> rust/kernel/kunit.rs | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/rust/kernel/kunit.rs b/rust/kernel/kunit.rs
> index f93f24a60bdd..5da342f5c84a 100644
> --- a/rust/kernel/kunit.rs
> +++ b/rust/kernel/kunit.rs
> @@ -13,6 +13,8 @@
> ///
> /// Public but hidden since it should only be used from KUnit generated code.
> #[doc(hidden)]
> +// `args` is unused if `CONFIG_PRINTK` is not set.
> +#[allow(unused_variables)]
> pub fn err(args: fmt::Arguments<'_>) {
> // SAFETY: The format string is null-terminated and the `%pA` specifier matches the argument we
> // are passing.
> @@ -29,6 +31,8 @@ pub fn err(args: fmt::Arguments<'_>) {
> ///
> /// Public but hidden since it should only be used from KUnit generated code.
> #[doc(hidden)]
> +// `args` is unused if `CONFIG_PRINTK` is not set.
> +#[allow(unused_variables)]
> pub fn info(args: fmt::Arguments<'_>) {
> // SAFETY: The format string is null-terminated and the `%pA` specifier matches the argument we
> // are passing.
>
> ---
> base-commit: 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f
> change-id: 20260224-unused_var_err-996d7ffa27c5
>
> Best regards,
prev parent reply other threads:[~2026-02-24 9:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 7:45 Alexandre Courbot
2026-02-24 7:49 ` Alice Ryhl
2026-02-24 7:52 ` Alice Ryhl
2026-02-24 12:57 ` Andreas Hindborg
2026-02-24 9:01 ` David Gow [this message]
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=b963ea9b-69d5-4d4e-8c1d-8e969c545a79@davidgow.net \
--to=david@davidgow.net \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=brendan.higgins@linux.dev \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=raemoar63@gmail.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=skhan@linuxfoundation.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®