From: Andreas Hindborg <a.hindborg@kernel.org>
To: FUJITA Tomonori <fujita.tomonori@gmail.com>
Cc: rust-for-linux@vger.kernel.org, boqun.feng@gmail.com,
frederic@kernel.org, lyude@redhat.com, tglx@linutronix.de,
anna-maria@linutronix.de, jstultz@google.com, sboyd@kernel.org,
ojeda@kernel.org, alex.gaynor@gmail.com, gary@garyguo.net,
bjorn3_gh@protonmail.com, benno.lossin@proton.me,
aliceryhl@google.com, tmgross@umich.edu, dakr@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/3] rust: time: Make Instant generic over ClockSource
Date: Fri, 30 May 2025 13:42:04 +0200 [thread overview]
Message-ID: <87jz5y1g1f.fsf@kernel.org> (raw)
In-Reply-To: <20250504042436.237756-3-fujita.tomonori@gmail.com> (FUJITA Tomonori's message of "Sun, 4 May 2025 13:24:34 +0900")
FUJITA Tomonori <fujita.tomonori@gmail.com> writes:
> Refactor the Instant type to be generic over a ClockSource type
> parameter, enabling static enforcement of clock correctness across
> APIs that deal with time. Previously, the clock source was implicitly
> fixed (typically CLOCK_MONOTONIC), and developers had to ensure
> compatibility manually.
>
> This design eliminates runtime mismatches between clock sources, and
> enables stronger type-level guarantees throughout the timer subsystem.
>
> Signed-off-by: FUJITA Tomonori <fujita.tomonori@gmail.com>
Reviewed-by: Andreas Hindborg <a.hindborg@kernel.org>
Best regards,
Andreas Hindborg
next prev parent reply other threads:[~2025-05-30 11:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-04 4:24 [PATCH v2 0/3] rust: time: Introduce typed clock sources and generalize Instant FUJITA Tomonori
2025-05-04 4:24 ` [PATCH v2 1/3] rust: time: Replace ClockId enum with ClockSource trait FUJITA Tomonori
2025-05-04 4:24 ` [PATCH v2 2/3] rust: time: Make Instant generic over ClockSource FUJITA Tomonori
2025-05-30 11:42 ` Andreas Hindborg [this message]
2025-05-04 4:24 ` [PATCH v2 3/3] rust: time: Add ktime_get() to ClockSource trait FUJITA Tomonori
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=87jz5y1g1f.fsf@kernel.org \
--to=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=anna-maria@linutronix.de \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=frederic@kernel.org \
--cc=fujita.tomonori@gmail.com \
--cc=gary@garyguo.net \
--cc=jstultz@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=sboyd@kernel.org \
--cc=tglx@linutronix.de \
--cc=tmgross@umich.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.