From: Andreas Hindborg <a.hindborg@kernel.org>
To: rust-for-linux@vger.kernel.org,
FUJITA Tomonori <fujita.tomonori@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>, Boqun Feng <boqun.feng@gmail.com>,
linux-kernel@vger.kernel.org, frederic@kernel.org,
lyude@redhat.com, tglx@linutronix.de, anna-maria@linutronix.de,
jstultz@google.com, sboyd@kernel.org, ojeda@kernel.org,
alex.gaynor@gmail.com, gary@garyguo.net,
bjorn3_gh@protonmail.com, aliceryhl@google.com,
tmgross@umich.edu, chrisi.schrefl@gmail.com,
linux@armlinux.org.uk, Andreas Hindborg <a.hindborg@kernel.org>,
Benno Lossin <lossin@kernel.org>
Subject: Re: [PATCH v2] rust: time: Avoid 64-bit integer division on 32-bit architectures
Date: Tue, 17 Jun 2025 12:37:48 +0200 [thread overview]
Message-ID: <175015666839.277659.16490602570734103126.b4-ty@kernel.org> (raw)
In-Reply-To: <20250502004524.230553-1-fujita.tomonori@gmail.com>
On Fri, 02 May 2025 09:45:24 +0900, FUJITA Tomonori wrote:
> Avoid 64-bit integer division that 32-bit architectures don't
> implement generally. This uses ktime_to_us() and ktime_to_ms()
> instead.
>
> The time abstraction needs i64 / u32 division so C's div_s64() can be
> used but ktime_to_us() and ktime_to_ms() provide a simpler solution
> for this time abstraction problem on 32-bit architectures.
>
> [...]
Applied, thanks!
[1/1] rust: time: Avoid 64-bit integer division on 32-bit architectures
commit: 1b7bbd5975279a1cf8d907fbc719f350031194c2
Best regards,
--
Andreas Hindborg <a.hindborg@kernel.org>
prev parent reply other threads:[~2025-06-17 10:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-02 0:45 FUJITA Tomonori
2025-05-28 18:24 ` Andreas Hindborg
2025-06-17 10:37 ` 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=175015666839.277659.16490602570734103126.b4-ty@kernel.org \
--to=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=anna-maria@linutronix.de \
--cc=arnd@arndb.de \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=chrisi.schrefl@gmail.com \
--cc=frederic@kernel.org \
--cc=fujita.tomonori@gmail.com \
--cc=gary@garyguo.net \
--cc=jstultz@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--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@linutronix.de \
--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®