From: FUJITA Tomonori <tomo@flapping.org>
To: miguel.ojeda.sandonis@gmail.com
Cc: tomo@flapping.org, ojeda@kernel.org, arnd@arndb.de,
krzk@kernel.org, alexandre.belloni@bootlin.com,
linusw@kernel.org, chenhuacai@kernel.org, boqun@kernel.org,
gary@garyguo.net, bjorn3_gh@protonmail.com, lossin@kernel.org,
a.hindborg@kernel.org, aliceryhl@google.com, tmgross@umich.edu,
dakr@kernel.org, daniel.almeida@collabora.com, tamird@kernel.org,
acourbot@nvidia.com, work@onurozkan.dev,
rust-for-linux@vger.kernel.org, fustini@kernel.org,
linux-arm-kernel@lists.infradead.org, soc@lists.linux.dev,
kernel@xen0n.name, loongarch@lists.linux.dev,
stable@vger.kernel.org
Subject: Re: [PATCH] rust: bug: fix `dead_code` warning in `warn_on!`
Date: Sun, 09 Aug 2026 09:50:41 +0900 (JST) [thread overview]
Message-ID: <20260809.095041.602618436881623934.tomo@flapping.org> (raw)
In-Reply-To: <CANiq72m70uWCRFnhs3axdymSTGCirBrYAvKh2BiT0xqW2j_3jg@mail.gmail.com>
On Sat, 8 Aug 2026 21:40:49 +0200
Miguel Ojeda <miguel.ojeda.sandonis@gmail.com> wrote:
>> I posted a `cfg(testlib)` split for it:
>>
>> https://lore.kernel.org/all/20260808022608.1125174-1-tomo@flapping.org/
>
> Thanks! It seems good to me.
Thanks!
>> While at it, a question: what is `rusttest` meant to cover when
>> `ARCH=` is not the host's?
>
> `rusttest` is meant to run tests on the host, regardless of the target.
Then `jump_label.rs` needs the same treatment?
`arch_static_branch!` embeds the generated arch asm too. It is not a
problem today only because, like `warn_on!` until now, it has no user
inside the `kernel` crate itself.
next prev parent reply other threads:[~2026-08-09 0:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 22:14 [PATCH] rust: bug: fix `dead_code` warning in `warn_on!` Miguel Ojeda
2026-08-07 22:19 ` Miguel Ojeda
2026-08-07 22:43 ` FUJITA Tomonori
2026-08-07 23:21 ` Miguel Ojeda
2026-08-08 5:30 ` FUJITA Tomonori
2026-08-08 19:40 ` Miguel Ojeda
2026-08-09 0:50 ` FUJITA Tomonori [this message]
2026-08-09 3:01 ` Miguel Ojeda
2026-08-09 14:41 ` Gary Guo
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=20260809.095041.602618436881623934.tomo@flapping.org \
--to=tomo@flapping.org \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=alexandre.belloni@bootlin.com \
--cc=aliceryhl@google.com \
--cc=arnd@arndb.de \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=chenhuacai@kernel.org \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=fustini@kernel.org \
--cc=gary@garyguo.net \
--cc=kernel@xen0n.name \
--cc=krzk@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=loongarch@lists.linux.dev \
--cc=lossin@kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=soc@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=tamird@kernel.org \
--cc=tmgross@umich.edu \
--cc=work@onurozkan.dev \
/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