Re: [PATCH] rust: bug: fix `dead_code` warning in `warn_on!`
Miguel Ojeda <[email protected]>
| Newsgroups | org.kernel.vger.rust-for-linux,dev.linux.lists.loongarch,dev.linux.lists.soc,org.infradead.lists.linux-arm-kernel,org.kernel.vger.stable |
|---|---|
| Message-ID | <CANiq72m70uWCRFnhs3axdymSTGCirBrYAvKh2BiT0xqW2j_3jg@mail.gmail.com> |
On Sat, Aug 8, 2026 at 7:30 AM FUJITA Tomonori <[email protected]> wrote: > > Is this the one you saw? Yeah, exactly. > I posted a `cfg(testlib)` split for it: > > https://lore.kernel.org/all/[email protected]/ Thanks! It seems good to me. > 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. There aren't many tests there nowadays, since most of them moved to the actual kernel when we got support for that, but we can still do there things like testing proc macros. We could also use it for more things in the future, perhaps... Cheers, Miguel