From: Andreas Hindborg <a.hindborg@kernel.org>
To: "Miguel Ojeda" <miguel.ojeda.sandonis@gmail.com>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun.feng@gmail.com>,
"FUJITA Tomonori" <fujita.tomonori@gmail.com>,
"Frederic Weisbecker" <frederic@kernel.org>,
"Lyude Paul" <lyude@redhat.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Anna-Maria Behnsen" <anna-maria@linutronix.de>,
"John Stultz" <jstultz@google.com>,
"Stephen Boyd" <sboyd@kernel.org>,
"rust-for-linux@vger.kernel.org"
<rust-for-linux@vger.kernel.org>
Subject: Re: [GIT PULL] Rust timekeeping for v6.17
Date: Tue, 15 Jul 2025 09:57:53 +0200 [thread overview]
Message-ID: <87wm89hon2.fsf@kernel.org> (raw)
In-Reply-To: <CANiq72mP7QAjnYuM44tu0ZaviWO4PNWV6Oba=LMwh8=FxJJU1w@mail.gmail.com> (Miguel Ojeda's message of "Mon, 14 Jul 2025 00:04:20 +0200")
Hi Miguel,
"Miguel Ojeda" <miguel.ojeda.sandonis@gmail.com> writes:
> On Mon, Jul 7, 2025 at 9:47 AM Andreas Hindborg <a.hindborg@kernel.org> wrote:
>>
>> ----------------------------------------------------------------
>> rust-timekeeping for v6.17
>>
>> ----------------------------------------------------------------
>
> The description is empty -- could you please provide a bit of text?
>
> No need to send a new PR, since I know you may be away from your usual
> office these days -- I can copy it from email.
>
> (Worst case, I will write something myself, but there is still time.)
>
Sorry for the missing tag text. Let me know if you can use the following
bullets:
- Make `Instant` generic over clock source. This allows the compiler to
assert that arithmetic expressions involving the `Instant` use
`Instants` based on the same clock source.
- Make `HrTimer` generic over the timer mode. `HrTimer` timers take a
`Duration` or an `Instant` when setting the expiry time, depending on the
timer mode. With this change, the compiler can check the type matches the
timer mode.
- Add an abstraction for `fsleep`. `fsleep` is a flexible sleep function that
will select an appropriate sleep method depending on the requested sleep
time.
- Avoid 64-bit divisions on 32-bit hardware when calculating timestamps.
- Seal the `HrTimerMode` trait. This prevents users of the
`HrTimerMode` from implementing the trait on their own types.
Best regards,
Andreas Hindborg
next prev parent reply other threads:[~2025-07-15 7:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-07 7:46 [GIT PULL] Rust timekeeping for v6.17 Andreas Hindborg
2025-07-13 22:04 ` Miguel Ojeda
2025-07-15 7:57 ` Andreas Hindborg [this message]
2025-07-15 12:13 ` Miguel Ojeda
2025-07-17 0:02 ` Miguel Ojeda
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=87wm89hon2.fsf@kernel.org \
--to=a.hindborg@kernel.org \
--cc=anna-maria@linutronix.de \
--cc=boqun.feng@gmail.com \
--cc=frederic@kernel.org \
--cc=fujita.tomonori@gmail.com \
--cc=jstultz@google.com \
--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=tglx@linutronix.de \
/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.