[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72kL_4=5LwGtJ-67djXzOyjn7VsZsvStUky=JAv4sdS-uw@mail.gmail.com>
Date: Thu, 31 Jul 2025 23:12:20 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Lyude Paul <lyude@...hat.com>
Cc: Alice Ryhl <aliceryhl@...gle.com>, 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 2/2] rust: time: Implement basic arithmetic operations for Delta
On Thu, Jul 31, 2025 at 10:47 PM Lyude Paul <lyude@...hat.com> wrote:
>
> Gotcha, I will do that. Ideally I would at least like to have us only call the
> bindings:: method so long as we're on a config where we really need it. Which
> brings me to ask - do we actually have a way of checking BITS_PER_LONG in
> #[cfg()]? I would have assumed it'd be simple but I don't actually seem to be
> able to reference BITS_PER_LONG.
It is not in the config, so we don't have it. We could add it if you
think it is really useful, but it is based on `CONFIG_64BIT` anyway,
no?
Cheers,
Miguel
Powered by blists - more mailing lists