Re: [PATCH] rust: bug: fix `dead_code` warning in `warn_on!`
FUJITA Tomonori <[email protected]>
| Newsgroups | dev.linux.lists.soc,dev.linux.lists.loongarch,org.infradead.lists.linux-arm-kernel,org.kernel.vger.rust-for-linux,org.kernel.vger.stable |
|---|---|
| Message-ID | <[email protected]> |
On Sat, 8 Aug 2026 21:40:49 +0200 Miguel Ojeda <[email protected]> wrote: >> I posted a `cfg(testlib)` split for it: >> >> https://lore.kernel.org/all/[email protected]/ > > 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.