From: Andreas Hindborg <a.hindborg@kernel.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
David Gow <david@davidgow.net>
Cc: FUJITA Tomonori <tomo@flapping.org>,
gary@garyguo.net, ojeda@kernel.org, acourbot@nvidia.com,
aliceryhl@google.com, anna-maria@linutronix.de,
bjorn3_gh@protonmail.com, boqun@kernel.org, dakr@kernel.org,
daniel.almeida@collabora.com, frederic@kernel.org,
jstultz@google.com, lossin@kernel.org, lyude@redhat.com,
sboyd@kernel.org, tamird@kernel.org, tglx@kernel.org,
tmgross@umich.edu, work@onurozkan.dev,
rust-for-linux@vger.kernel.org, fujita.tomonori@gmail.com,
Yury Norov <yury.norov@gmail.com>
Subject: Re: [PATCH v4 2/2] rust: time: add Delta::to_jiffies_timeout() for timeout conversion
Date: Mon, 28 Sep 2026 11:57:37 +0200 [thread overview]
Message-ID: <87ecedu29a.fsf@t14s.mail-host-address-is-not-set> (raw)
In-Reply-To: <CANiq72mUWhzwZhDpDTj7awy=WN4vcSKF+PKbbAA1YTMX-sW2Ew@mail.gmail.com>
"Miguel Ojeda" <miguel.ojeda.sandonis@gmail.com> writes:
> On Mon, Sep 28, 2026 at 11:37 AM Andreas Hindborg <a.hindborg@kernel.org> wrote:
>>
>> I would prefer to just enable the tests as soon as kunit is enabled if
>> that is OK.
>
> Let me Cc David (and Yury) to see what he thinks -- the kernel
> probably wants to have at least a Kconfig for each test rather than
> having a default set that gets always enabled as soon as KUnit test, I
> think the question is mostly about how "wide" to make those Kconfigs.
I'm used to having all the rust tests enabled when I hack on rust stuff.
I would rather not have to go flick a ton of switches to enable all the
stuff.
I think that most users that enable rust+kunit will be fine with
enabling all rust kunit tests. I understand that there may be
environments like embedded platforms where this is not feasible. Could
we invert the situation so that we have one toggle to enable all our
tests but make it possible to opt out of this behavior?
RUST=y
KUNIT=y
RUST_ALL_KUNIT_TESTS=y
That would be great.
Best regards,
Andreas Hindborg
next prev parent reply other threads:[~2026-09-28 9:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 23:25 [PATCH v4 0/2] Add Delta::to_jiffies_timeout() FUJITA Tomonori
2026-09-24 23:25 ` [PATCH v4 1/2] rust: bindings: set HZ to CONFIG_HZ FUJITA Tomonori
2026-09-24 23:25 ` [PATCH v4 2/2] rust: time: add Delta::to_jiffies_timeout() for timeout conversion FUJITA Tomonori
2026-09-25 8:00 ` Andreas Hindborg
2026-09-25 9:39 ` FUJITA Tomonori
2026-09-25 14:48 ` Miguel Ojeda
2026-09-28 9:37 ` Andreas Hindborg
2026-09-28 9:45 ` Miguel Ojeda
2026-09-28 9:57 ` Andreas Hindborg [this message]
2026-09-29 10:15 ` [PATCH v4 0/2] Add Delta::to_jiffies_timeout() Andreas Hindborg
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=87ecedu29a.fsf@t14s.mail-host-address-is-not-set \
--to=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=anna-maria@linutronix.de \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=david@davidgow.net \
--cc=frederic@kernel.org \
--cc=fujita.tomonori@gmail.com \
--cc=gary@garyguo.net \
--cc=jstultz@google.com \
--cc=lossin@kernel.org \
--cc=lyude@redhat.com \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=sboyd@kernel.org \
--cc=tamird@kernel.org \
--cc=tglx@kernel.org \
--cc=tmgross@umich.edu \
--cc=tomo@flapping.org \
--cc=work@onurozkan.dev \
--cc=yury.norov@gmail.com \
/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