From: David Gow <david@davidgow.net>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
Alexandre Courbot <acourbot@nvidia.com>
Cc: "Brendan Higgins" <brendan.higgins@linux.dev>,
"David Gow" <davidgow@google.com>,
"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>,
linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] rust: kunit: fix warning when !CONFIG_PRINTK
Date: Wed, 4 Mar 2026 17:16:19 +0800 [thread overview]
Message-ID: <cccf55e9-e744-4581-9c14-ffa54bc90faf@davidgow.net> (raw)
In-Reply-To: <CANiq72kROq3B=EPfihKM=bvtyqYrbDV-mkFgROdPNjbC6zaBpQ@mail.gmail.com>
Le 04/03/2026 à 10:34 AM, Miguel Ojeda a écrit :
> On Tue, Feb 24, 2026 at 11:38 AM Alexandre Courbot <acourbot@nvidia.com> wrote:
>>
>> 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 adding a no-op assignment using `args` when `CONFIG_PRINTK`
>> is not set.
>>
>> Fixes: a66d733da801 ("rust: support running Rust documentation tests as KUnit ones")
>> Signed-off-by: Alexandre Courbot <acourbot@nvidia.com>
>
> Applied to `rust-fixes` -- thanks everyone!
>
> Also Cc: stable@vger.kernel.org
This is also sitting in kselftest/kunit-fixes:
https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git/commit/?h=kunit-fixes&id=7dd34dfc8dfa92a7244242098110388367996ac3
I don't particularly mind if you'd rather it go through the Rust tree,
though. Let me know if you want this removed.
Cheers,
-- David
next prev parent reply other threads:[~2026-03-04 9:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Qrs5fItWst004EC_jGHvnTB2s8QuVM9cnRKIhUuImhaSV8qhL9DmqifhAqLFPSEf1JYNS9J-1hWqvptIARahvQ==@protonmail.internalid>
2026-02-24 10:37 ` [PATCH v2] rust: kunit: fix warning when !CONFIG_PRINTK Alexandre Courbot
2026-02-24 11:44 ` Alice Ryhl
2026-02-24 11:51 ` Andreas Hindborg
2026-02-24 13:07 ` Alexandre Courbot
2026-02-24 13:15 ` Alice Ryhl
2026-02-24 13:56 ` David Gow
2026-02-24 14:23 ` Alexandre Courbot
2026-02-24 13:56 ` David Gow
2026-03-04 2:34 ` Miguel Ojeda
2026-03-04 9:16 ` David Gow [this message]
2026-03-04 12:07 ` Miguel Ojeda
2026-03-05 23:55 ` Miguel Ojeda
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=cccf55e9-e744-4581-9c14-ffa54bc90faf@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=davidgow@google.com \
--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=miguel.ojeda.sandonis@gmail.com \
--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