* [GIT PULL] Rust timekeeping for v7.4-rc1
@ 2026-10-07 13:34 Andreas Hindborg
2026-10-07 13:55 ` FUJITA Tomonori
2026-10-12 5:09 ` Miguel Ojeda
0 siblings, 2 replies; 5+ messages in thread
From: Andreas Hindborg @ 2026-10-07 13:34 UTC (permalink / raw)
To: Miguel Ojeda
Cc: Boqun Feng, FUJITA Tomonori, Frederic Weisbecker, Lyude Paul,
Thomas Gleixner, Anna-Maria Behnsen, John Stultz, Stephen Boyd,
rust-for-linux@vger.kernel.org, rust-for-linux
Hi Miguel,
Please pull these changes for rust timekeeping for v7.4-rc1.
The following changes since commit df2908090cda368b01ff43709f51890076c56157:
Linux 7.3-rc2 (2026-09-06 15:07:20 -0700)
are available in the Git repository at:
https://github.com/rust-for-linux/linux.git tags/rust-timekeeping-for-v7.4-rc1
for you to fetch changes up to 2ea0119f72dba597aa8a98cbdb72c564bfc5cb38:
rust: hrtimer: document handle based design rationale (2026-09-29 09:22:30 +0200)
----------------------------------------------------------------
Rust timekeeping changes for v7.4-rc1
This time we have a few assorted changes:
- Warnings when passing out-of-range inputs to `fsleep` and `udelay`.
- Rename `ClockSource` to `ClockId` to better align with naming conventions in C kernel.
- Make `CONFIG_HZ` value available as `bindings::HZ`.
- Add a conversion method to convert `Delta` to `jiffies` for use in timeout arguments.
- Add implementation detail documentation for `HrTimer`.
----------------------------------------------------------------
Andreas Hindborg (1):
rust: hrtimer: document handle based design rationale
FUJITA Tomonori (3):
rust: time: rename ClockSource trait to ClockId
rust: bindings: set HZ to CONFIG_HZ
rust: time: add Delta::to_jiffies_timeout() for timeout conversion
Sang-Heon Jeon (1):
rust: time: warn and assert out-of-range input in fsleep() and udelay()
rust/bindings/lib.rs | 5 ++
rust/helpers/helpers.c | 1 +
rust/helpers/math.c | 8 +++
rust/kernel/Kconfig.test | 10 ++++
rust/kernel/time.rs | 139 ++++++++++++++++++++++++++++++++++++++------
rust/kernel/time/delay.rs | 17 ++++--
rust/kernel/time/hrtimer.rs | 95 +++++++++++++++++-------------
7 files changed, 211 insertions(+), 64 deletions(-)
create mode 100644 rust/helpers/math.c
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [GIT PULL] Rust timekeeping for v7.4-rc1
2026-10-07 13:34 [GIT PULL] Rust timekeeping for v7.4-rc1 Andreas Hindborg
@ 2026-10-07 13:55 ` FUJITA Tomonori
2026-10-08 13:02 ` Andreas Hindborg
2026-10-12 5:09 ` Miguel Ojeda
1 sibling, 1 reply; 5+ messages in thread
From: FUJITA Tomonori @ 2026-10-07 13:55 UTC (permalink / raw)
To: a.hindborg, ojeda
Cc: boqun.feng, fujita.tomonori, frederic, lyude, tglx, anna-maria,
jstultz, sboyd, rust-for-linux
Hi Andreas,
On Wed, 07 Oct 2026 15:34:44 +0200
Andreas Hindborg <a.hindborg@kernel.org> wrote:
> Hi Miguel,
>
> Please pull these changes for rust timekeeping for v7.4-rc1.
>
> The following changes since commit df2908090cda368b01ff43709f51890076c56157:
>
> Linux 7.3-rc2 (2026-09-06 15:07:20 -0700)
>
> are available in the Git repository at:
>
> https://github.com/rust-for-linux/linux.git tags/rust-timekeeping-for-v7.4-rc1
>
> for you to fetch changes up to 2ea0119f72dba597aa8a98cbdb72c564bfc5cb38:
>
> rust: hrtimer: document handle based design rationale (2026-09-29 09:22:30 +0200)
>
> ----------------------------------------------------------------
> Rust timekeeping changes for v7.4-rc1
>
> This time we have a few assorted changes:
>
> - Warnings when passing out-of-range inputs to `fsleep` and `udelay`.
> - Rename `ClockSource` to `ClockId` to better align with naming conventions in C kernel.
> - Make `CONFIG_HZ` value available as `bindings::HZ`.
> - Add a conversion method to convert `Delta` to `jiffies` for use in timeout arguments.
> - Add implementation detail documentation for `HrTimer`.
>
> ----------------------------------------------------------------
> Andreas Hindborg (1):
> rust: hrtimer: document handle based design rationale
>
> FUJITA Tomonori (3):
> rust: time: rename ClockSource trait to ClockId
> rust: bindings: set HZ to CONFIG_HZ
> rust: time: add Delta::to_jiffies_timeout() for timeout conversion
>
> Sang-Heon Jeon (1):
> rust: time: warn and assert out-of-range input in fsleep() and udelay()
Would it be possible to also include the following two patches in this
pull request?
rust: time: make Delta::ZERO generic over the time unit
rust: time: add Delta::as_jiffies_unsigned()
https://lore.kernel.org/rust-for-linux/20261002050428.2746277-2-tomo@flapping.org/
https://lore.kernel.org/rust-for-linux/20261002050428.2746277-3-tomo@flapping.org/
Three patches depend on them: the workqueue and condvar patches in the
same series, and the serdev patch. All three change code that is
merged through trees other than rust-next. If the two patches are in
v7.4-rc1, the three patches can go through those trees in the next
cycle without a dependency on the timekeeping tree.
Both patches are small and straightforward, and Gary has already given
his Reviewed-by.
If it is easier, Miguel could also apply them to rust-next directly
with your Acked-by. That would work for me too.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [GIT PULL] Rust timekeeping for v7.4-rc1
2026-10-07 13:55 ` FUJITA Tomonori
@ 2026-10-08 13:02 ` Andreas Hindborg
2026-10-08 13:40 ` FUJITA Tomonori
0 siblings, 1 reply; 5+ messages in thread
From: Andreas Hindborg @ 2026-10-08 13:02 UTC (permalink / raw)
To: FUJITA Tomonori, ojeda
Cc: boqun.feng, fujita.tomonori, frederic, lyude, tglx, anna-maria,
jstultz, sboyd, rust-for-linux
"FUJITA Tomonori" <tomo@flapping.org> writes:
> Hi Andreas,
>
> On Wed, 07 Oct 2026 15:34:44 +0200
> Andreas Hindborg <a.hindborg@kernel.org> wrote:
>
>> Hi Miguel,
>>
>> Please pull these changes for rust timekeeping for v7.4-rc1.
>>
>> The following changes since commit df2908090cda368b01ff43709f51890076c56157:
>>
>> Linux 7.3-rc2 (2026-09-06 15:07:20 -0700)
>>
>> are available in the Git repository at:
>>
>> https://github.com/rust-for-linux/linux.git tags/rust-timekeeping-for-v7.4-rc1
>>
>> for you to fetch changes up to 2ea0119f72dba597aa8a98cbdb72c564bfc5cb38:
>>
>> rust: hrtimer: document handle based design rationale (2026-09-29 09:22:30 +0200)
>>
>> ----------------------------------------------------------------
>> Rust timekeeping changes for v7.4-rc1
>>
>> This time we have a few assorted changes:
>>
>> - Warnings when passing out-of-range inputs to `fsleep` and `udelay`.
>> - Rename `ClockSource` to `ClockId` to better align with naming conventions in C kernel.
>> - Make `CONFIG_HZ` value available as `bindings::HZ`.
>> - Add a conversion method to convert `Delta` to `jiffies` for use in timeout arguments.
>> - Add implementation detail documentation for `HrTimer`.
>>
>> ----------------------------------------------------------------
>> Andreas Hindborg (1):
>> rust: hrtimer: document handle based design rationale
>>
>> FUJITA Tomonori (3):
>> rust: time: rename ClockSource trait to ClockId
>> rust: bindings: set HZ to CONFIG_HZ
>> rust: time: add Delta::to_jiffies_timeout() for timeout conversion
>>
>> Sang-Heon Jeon (1):
>> rust: time: warn and assert out-of-range input in fsleep() and udelay()
>
> Would it be possible to also include the following two patches in this
> pull request?
>
> rust: time: make Delta::ZERO generic over the time unit
> rust: time: add Delta::as_jiffies_unsigned()
>
> https://lore.kernel.org/rust-for-linux/20261002050428.2746277-2-tomo@flapping.org/
> https://lore.kernel.org/rust-for-linux/20261002050428.2746277-3-tomo@flapping.org/
>
> Three patches depend on them: the workqueue and condvar patches in the
> same series, and the serdev patch. All three change code that is
> merged through trees other than rust-next. If the two patches are in
> v7.4-rc1, the three patches can go through those trees in the next
> cycle without a dependency on the timekeeping tree.
>
> Both patches are small and straightforward, and Gary has already given
> his Reviewed-by.
>
> If it is easier, Miguel could also apply them to rust-next directly
> with your Acked-by. That would work for me too.
I'm not taking any more changes for timekeeping this cycle. Up to Miguel
if he wants to take them directly. Otherwise wait for next cycle. Either
is fine with me.
Best regards,
Andreas Hindborg
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [GIT PULL] Rust timekeeping for v7.4-rc1
2026-10-08 13:02 ` Andreas Hindborg
@ 2026-10-08 13:40 ` FUJITA Tomonori
0 siblings, 0 replies; 5+ messages in thread
From: FUJITA Tomonori @ 2026-10-08 13:40 UTC (permalink / raw)
To: a.hindborg, ojeda
Cc: tomo, boqun.feng, fujita.tomonori, frederic, lyude, tglx,
anna-maria, jstultz, sboyd, rust-for-linux
On Thu, 08 Oct 2026 15:02:51 +0200
Andreas Hindborg <a.hindborg@kernel.org> wrote:
> "FUJITA Tomonori" <tomo@flapping.org> writes:
>
>> Hi Andreas,
>>
>> On Wed, 07 Oct 2026 15:34:44 +0200
>> Andreas Hindborg <a.hindborg@kernel.org> wrote:
[...]
>>> ----------------------------------------------------------------
>>> Andreas Hindborg (1):
>>> rust: hrtimer: document handle based design rationale
>>>
>>> FUJITA Tomonori (3):
>>> rust: time: rename ClockSource trait to ClockId
>>> rust: bindings: set HZ to CONFIG_HZ
>>> rust: time: add Delta::to_jiffies_timeout() for timeout conversion
>>>
>>> Sang-Heon Jeon (1):
>>> rust: time: warn and assert out-of-range input in fsleep() and udelay()
>>
>> Would it be possible to also include the following two patches in this
>> pull request?
>>
>> rust: time: make Delta::ZERO generic over the time unit
>> rust: time: add Delta::as_jiffies_unsigned()
>>
>> https://lore.kernel.org/rust-for-linux/20261002050428.2746277-2-tomo@flapping.org/
>> https://lore.kernel.org/rust-for-linux/20261002050428.2746277-3-tomo@flapping.org/
>>
>> Three patches depend on them: the workqueue and condvar patches in the
>> same series, and the serdev patch. All three change code that is
>> merged through trees other than rust-next. If the two patches are in
>> v7.4-rc1, the three patches can go through those trees in the next
>> cycle without a dependency on the timekeeping tree.
>>
>> Both patches are small and straightforward, and Gary has already given
>> his Reviewed-by.
>>
>> If it is easier, Miguel could also apply them to rust-next directly
>> with your Acked-by. That would work for me too.
>
> I'm not taking any more changes for timekeeping this cycle. Up to Miguel
> if he wants to take them directly. Otherwise wait for next cycle. Either
> is fine with me.
Thanks, Andreas.
Miguel, could you take the two patches into rust-next directly?
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [GIT PULL] Rust timekeeping for v7.4-rc1
2026-10-07 13:34 [GIT PULL] Rust timekeeping for v7.4-rc1 Andreas Hindborg
2026-10-07 13:55 ` FUJITA Tomonori
@ 2026-10-12 5:09 ` Miguel Ojeda
1 sibling, 0 replies; 5+ messages in thread
From: Miguel Ojeda @ 2026-10-12 5:09 UTC (permalink / raw)
To: Andreas Hindborg
Cc: Miguel Ojeda, Boqun Feng, FUJITA Tomonori, Frederic Weisbecker,
Lyude Paul, Thomas Gleixner, Anna-Maria Behnsen, John Stultz,
Stephen Boyd, rust-for-linux@vger.kernel.org
On Wed, Oct 7, 2026 at 3:40 PM Andreas Hindborg <a.hindborg@kernel.org> wrote:
>
> Hi Miguel,
>
> Please pull these changes for rust timekeeping for v7.4-rc1.
>
> The following changes since commit df2908090cda368b01ff43709f51890076c56157:
>
> Linux 7.3-rc2 (2026-09-06 15:07:20 -0700)
>
> are available in the Git repository at:
>
> https://github.com/rust-for-linux/linux.git tags/rust-timekeeping-for-v7.4-rc1
>
> for you to fetch changes up to 2ea0119f72dba597aa8a98cbdb72c564bfc5cb38:
>
> rust: hrtimer: document handle based design rationale (2026-09-29 09:22:30 +0200)
Merged into `rust-next` -- thanks!
A couple notes:
- I had to fetch your updated GPG key. In case it helps: Linus and
other maintainers may expect to be told about the change when it
happens (and, in general, rotating them too often may not be
appreciated).
- Please try to have a main verb per bullet point in the merge
commit since that is the style that Linus prefers. Similarly, please
use ' instead of ` (only for these messages) and wrap the message like
a commit one. I tweaked the message a bit to match.
By the way, I wonder if we want to add `#` to the "Implementation
details" sections even if it is a `//` (like we do for the actual
`///` ones).
Cheers,
Miguel
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2026-10-12 5:09 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-10-07 13:34 [GIT PULL] Rust timekeeping for v7.4-rc1 Andreas Hindborg
2026-10-07 13:55 ` FUJITA Tomonori
2026-10-08 13:02 ` Andreas Hindborg
2026-10-08 13:40 ` FUJITA Tomonori
2026-10-12 5:09 ` Miguel Ojeda
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.