From: "Arnd Bergmann" <arnd@arndb.de>
To: "Nicolas Pitre" <nico@fluxnic.net>,
"Russell King" <linux@armlinux.org.uk>
Cc: "Nicolas Pitre" <npitre@baylibre.com>,
Linux-Arch <linux-arch@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/4] simplify do_div() with constant divisor
Date: Fri, 04 Oct 2024 13:25:11 +0000 [thread overview]
Message-ID: <75c272ce-b4dd-4360-9489-b9af33b87a33@app.fastmail.com> (raw)
In-Reply-To: <20241003211829.2750436-1-nico@fluxnic.net>
On Thu, Oct 3, 2024, at 21:16, Nicolas Pitre wrote:
> While working on mul_u64_u64_div_u64() improvements I realized that there
> is a better way to perform a 64x64->128 bits multiplication with overflow
> handling.
>
> Change from v3:
>
> - Added timings to commit log of patch #4.
>
> Link to v3:
> https://lore.kernel.org/lkml/20240708012749.2098373-2-nico@fluxnic.net/T/
Looks good to me. There are no other comments, I would apply this
in the asm-generic tree for 6.13.
Arnd
next prev parent reply other threads:[~2024-10-04 13:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-03 21:16 Nicolas Pitre
2024-10-03 21:16 ` [PATCH v4 1/4] lib/math/test_div64: add some edge cases relevant to __div64_const32() Nicolas Pitre
2024-10-03 21:16 ` [PATCH v4 2/4] asm-generic/div64: optimize/simplify __div64_const32() Nicolas Pitre
2024-10-04 22:47 ` kernel test robot
2024-10-03 21:16 ` [PATCH v4 3/4] ARM: div64: improve __arch_xprod_64() Nicolas Pitre
2024-10-03 21:16 ` [PATCH v4 4/4] __arch_xprod64(): make __always_inline when optimizing for performance Nicolas Pitre
2024-10-04 13:25 ` Arnd Bergmann [this message]
2024-10-26 0:36 ` [PATCH v4 0/4] simplify do_div() with constant divisor Nicolas Pitre
2024-10-26 10:04 ` Arnd Bergmann
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=75c272ce-b4dd-4360-9489-b9af33b87a33@app.fastmail.com \
--to=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=nico@fluxnic.net \
--cc=npitre@baylibre.com \
/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®