From: Andreas Hindborg <a.hindborg@kernel.org>
To: alex.gaynor@gmail.com, ojeda@kernel.org,
Boqun Feng <boqun@kernel.org>,
FUJITA Tomonori <fujita.tomonori@gmail.com>
Cc: aliceryhl@google.com, anna-maria@linutronix.de,
bjorn3_gh@protonmail.com, dakr@kernel.org, frederic@kernel.org,
gary@garyguo.net, jstultz@google.com,
linux-kernel@vger.kernel.org, lossin@kernel.org,
lyude@redhat.com, rust-for-linux@vger.kernel.org,
sboyd@kernel.org, tmgross@umich.edu,
Thomas Gleixner <tglx@kernel.org>
Subject: Re: [PATCH v1] rust: time: make ClockSource unsafe trait
Date: Mon, 23 Mar 2026 12:07:08 +0100 [thread overview]
Message-ID: <177426402884.828014.6767744559708475072.b4-ty@kernel.org> (raw)
In-Reply-To: <20250630131011.405219-1-fujita.tomonori@gmail.com>
On Mon, 30 Jun 2025 22:10:11 +0900, FUJITA Tomonori wrote:
> Mark the ClockSource trait as unsafe and document its safety
> requirements. Specifically, implementers must guarantee that their
> `ktime_get()` implementation returns a value in the inclusive range
> [0, KTIME_MAX].
>
> Update all existing implementations to use `unsafe impl` with
> corresponding safety comments.
>
> [...]
Applied, thanks!
[1/1] rust: time: make ClockSource unsafe trait
commit: 67b598db7ef107d80091c4c957694b9a2feffa4c
Best regards,
--
Andreas Hindborg <a.hindborg@kernel.org>
prev parent reply other threads:[~2026-03-23 11:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 13:10 FUJITA Tomonori
2025-06-30 13:33 ` Alice Ryhl
2025-06-30 23:39 ` FUJITA Tomonori
2025-07-02 8:38 ` Andreas Hindborg
2025-07-02 9:17 ` Andreas Hindborg
2025-07-02 9:50 ` Alice Ryhl
2025-07-04 0:07 ` FUJITA Tomonori
2025-07-04 6:42 ` Miguel Ojeda
2025-07-04 7:13 ` Andreas Hindborg
2026-03-23 11:07 ` Andreas Hindborg [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=177426402884.828014.6767744559708475072.b4-ty@kernel.org \
--to=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=anna-maria@linutronix.de \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--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=lossin@kernel.org \
--cc=lyude@redhat.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=sboyd@kernel.org \
--cc=tglx@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®