From: FUJITA Tomonori <tomo@flapping.org>
To: a.hindborg@kernel.org, ojeda@kernel.org
Cc: tomo@flapping.org, boqun.feng@gmail.com,
fujita.tomonori@gmail.com, frederic@kernel.org, lyude@redhat.com,
tglx@linutronix.de, anna-maria@linutronix.de, jstultz@google.com,
sboyd@kernel.org, rust-for-linux@vger.kernel.org
Subject: Re: [GIT PULL] Rust timekeeping for v7.4-rc1
Date: Thu, 08 Oct 2026 22:40:28 +0900 (JST) [thread overview]
Message-ID: <20261008.224028.1620344487807334383.tomo@flapping.org> (raw)
In-Reply-To: <87y0c8cpl0.fsf@kernel.org>
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?
prev parent reply other threads:[~2026-10-08 13:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [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=20261008.224028.1620344487807334383.tomo@flapping.org \
--to=tomo@flapping.org \
--cc=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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox