From: "Arnd Bergmann" <arnd@arndb.de>
To: "Nicolas Pitre" <nico@fluxnic.net>
Cc: "Russell King" <linux@armlinux.org.uk>,
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: Sat, 26 Oct 2024 10:04:09 +0000 [thread overview]
Message-ID: <5777a9f3-a56c-424f-8e02-6bc6af1af9e8@app.fastmail.com> (raw)
In-Reply-To: <463oq322-5p62-2293-q8pp-15p3507888pr@syhkavp.arg>
On Sat, Oct 26, 2024, at 00:36, Nicolas Pitre wrote:
> On Fri, 4 Oct 2024, Arnd Bergmann wrote:
>
>> 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.
>
> Hello Arnd, still no sign of those patches in the asm-generic tree nor
> the linux-next tree.
Thanks for the reminder, I've applied it now.
Arnd
prev parent reply other threads:[~2024-10-26 10:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-03 21:16 [PATCH v4 0/4] simplify do_div() with constant divisor 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 ` [PATCH v4 0/4] simplify do_div() with constant divisor Arnd Bergmann
2024-10-26 0:36 ` Nicolas Pitre
2024-10-26 10:04 ` Arnd Bergmann [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=5777a9f3-a56c-424f-8e02-6bc6af1af9e8@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 \
/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;
as well as URLs for NNTP newsgroup(s).