From: Andreas Hindborg <a.hindborg@kernel.org>
To: Miguel Ojeda <ojeda@kernel.org>
Cc: 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>,
rust-for-linux@vger.kernel.org
Subject: [GIT PULL] Rust timekeeping for v7.1
Date: Mon, 30 Mar 2026 11:28:25 +0200 [thread overview]
Message-ID: <87wlytwts6.fsf@kernel.org> (raw)
Hi Miguel,
Pleas pull these changes for rust timekeeping.
This PR expands the example section of `HrTimer`, adds a constructor for
`Delta` and marks `ClockSource` as unsafe to ensure only valid values
are returned by `ClockSource::ktime_get`.
The following changes since commit c369299895a591d96745d6492d4888259b004a9e:
Linux 7.0-rc5 (2026-03-22 14:42:17 -0700)
are available in the Git repository at:
https://github.com/rust-for-linux/linux.git tags/rust-timekeeping-for-v7.1
for you to fetch changes up to ddb1444d3335129ae87d9796ab1debf41c0ee51b:
hrtimer: add usage examples to documentation (2026-03-23 08:31:00 +0100)
----------------------------------------------------------------
Rust timekeeping changes for v7.1
- Expand the example section in the `HrTimer` documentation.
- Mark the `ClockSource` trait as unsafe to ensure valid values for `ktime_get()`.
- Add `Delta::from_nanos()`.
----------------------------------------------------------------
Andreas Hindborg (1):
hrtimer: add usage examples to documentation
FUJITA Tomonori (1):
rust: time: make ClockSource unsafe trait
Lyude Paul (1):
rust/time: Add Delta::from_nanos()
rust/kernel/time.rs | 32 ++++-
rust/kernel/time/hrtimer.rs | 336 ++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 362 insertions(+), 6 deletions(-)
reply other threads:[~2026-03-30 9:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87wlytwts6.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=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