From: "Gary Guo" <gary@garyguo.net>
To: "Miguel Ojeda" <miguel.ojeda.sandonis@gmail.com>,
"FUJITA Tomonori" <tomo@flapping.org>
Cc: <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 15:41:25 +0100 [thread overview]
Message-ID: <DKKHPMXA030Z.M58PRIVY8LC9@garyguo.net> (raw)
In-Reply-To: <CANiq72n4=fz=JNKY0Jdm8BnLa=RmHB2B7s0bO47YTJ7hygqBZg@mail.gmail.com>
On Sat Aug 8, 2026 at 12:21 AM BST, Miguel Ojeda wrote:
> On Sat, Aug 8, 2026 at 12:43 AM FUJITA Tomonori <tomo@flapping.org> wrote:
>>
>> I sent a fix for this bug a few days ago:
>>
>> https://lore.kernel.org/all/20260801024841.786664-1-tomo@flapping.org/
>
> Ah, right, sorry! I also saw another one with `rusttest` for arm64 and
> riscv64. Did you see that one? We probably need a `cfg(testlib)`
> split.
I am not sure how much value does `rusttest` still provide, given that KUnit can
test much more stuff in an actual envirionment. The fact that we have to do
special casing does suggest to me that we might want to remove it.
Best,
Gary
prev parent reply other threads:[~2026-08-09 14:41 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
2026-08-09 3:01 ` Miguel Ojeda
2026-08-09 14:41 ` Gary Guo [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=DKKHPMXA030Z.M58PRIVY8LC9@garyguo.net \
--to=gary@garyguo.net \
--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=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=tomo@flapping.org \
--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