[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAH5fLgioqkcaJ_M7q3CEERPniREidqnWxS1=_HM89mFN5=q=iQ@mail.gmail.com>
Date: Mon, 28 Jul 2025 20:23:23 +0200
From: Alice Ryhl <aliceryhl@...gle.com>
To: Lyude Paul <lyude@...hat.com>
Cc: rust-for-linux@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
Boqun Feng <boqun.feng@...il.com>, linux-kernel@...r.kernel.org,
Andreas Hindborg <a.hindborg@...nel.org>, FUJITA Tomonori <fujita.tomonori@...il.com>,
Frederic Weisbecker <frederic@...nel.org>, Anna-Maria Behnsen <anna-maria@...utronix.de>,
John Stultz <jstultz@...gle.com>, Stephen Boyd <sboyd@...nel.org>, Miguel Ojeda <ojeda@...nel.org>,
Alex Gaynor <alex.gaynor@...il.com>, Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <lossin@...nel.org>, Trevor Gross <tmgross@...ch.edu>,
Danilo Krummrich <dakr@...nel.org>
Subject: Re: [PATCH 1/2] rust: time: Implement Add<Delta>/Sub<Delta> for Instant
On Mon, Jul 28, 2025 at 8:21 PM Lyude Paul <lyude@...hat.com> wrote:
>
> On Sun, 2025-07-27 at 07:33 +0000, Alice Ryhl wrote:
> >
> > I'm not so sure what to think about this clamp logic. Maybe it is the
> > best way to go ...
>
> Yeah - I was kinda hoping the mailing list would give me the direction to go
> on this one. The other thing that I considered that might make more sense was
> instead to implement these so that when over/underflow checking is enabled we
> panic when we get a value out of the range of 0 to KTIME_MAX. Would that make
> more sense?
Well, it would certainly be more consistent.
What does your use-case need?
Alice
Powered by blists - more mailing lists