From: Matti Vaittinen <mazziesaccount@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
Lars-Peter Clausen <lars@metafoo.de>,
linux-kernel@vger.kernel.org,
David Laight <David.Laight@aculab.com>,
Subhajit Ghosh <subhajit.ghosh@tweaklogic.com>,
linux-iio@vger.kernel.org
Subject: Re: [RESEND PATCH v2] iio: gts-helper: Fix division loop
Date: Mon, 19 Feb 2024 09:18:48 +0200 [thread overview]
Message-ID: <06660242-ec6a-4bfe-adb0-da7f826c1634@gmail.com> (raw)
In-Reply-To: <20240216135812.07c9b769@jic23-huawei>
Hi Jonathan,
On 2/16/24 15:58, Jonathan Cameron wrote:
> On Mon, 12 Feb 2024 13:20:09 +0200
> Matti Vaittinen <mazziesaccount@gmail.com> wrote:
>
>> The loop based 64bit division may run for a long time when dividend is a
>> lot bigger than the divider. Replace the division loop by the
>> div64_u64() which implementation may be significantly faster.
>>
>> Signed-off-by: Matti Vaittinen <mazziesaccount@gmail.com>
>> Fixes: 38416c28e168 ("iio: light: Add gain-time-scale helpers")
>>
>> ---
>> This is a resend. Only change is the base which is now the v6.8-rc4 and
>> not the v6.8-rc1
> Given I'm not rushing this in, it is going via my togreg tree, so the
> rebase wasn't really helpful (thankfully didn't stop it applying).
Oh, I didn't think about it. Just thought I'll rebase to the most recent
tag. I see the point now that you mentioned it, thanks.
> Would have been fine to send a ping response to the first posting of it.
Ok. Some maintainers like Mark prefer getting full resend instead of a
ping because they don't keep the old messages/patches around. Reacting
to ping would require them to go and fetch the patch from lore - while
having full resend allows them to apply patch using their normal
work-flow. Or, at least I think this is how Mark told me couple of years
ago. I must admit that plenty of water has flown through the Oulu-river
since that, so maybe this has changed also for them.
Anyways, good to know your preference, thanks!
> I was leaving some time for David or Subhajit to have time to take
> another look, but guess they are either happy with this or busy.
Ok. This is perfectly fine. I just thought that maybe the patch fell
through the cracks and decided to re-send before I forget ... :)
> Applied to the togreg branch of iio.git and pushed out as testing for
> all the normal reasons.
Thanks!
Yours,
-- Matti
--
Matti Vaittinen
Linux kernel developer at ROHM Semiconductors
Oulu Finland
~~ When things go utterly wrong vim users can always type :help! ~~
prev parent reply other threads:[~2024-02-19 7:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 11:20 [RESEND PATCH v2] iio: gts-helper: Fix division loop Matti Vaittinen
2024-02-16 13:58 ` Jonathan Cameron
2024-02-17 14:39 ` Subhajit Ghosh
2024-02-17 16:27 ` Jonathan Cameron
2024-02-18 5:26 ` Subhajit Ghosh
2024-02-19 7:22 ` Matti Vaittinen
2024-02-19 19:32 ` Jonathan Cameron
2024-02-24 0:11 ` Subhajit Ghosh
2024-02-19 7:18 ` Matti Vaittinen [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=06660242-ec6a-4bfe-adb0-da7f826c1634@gmail.com \
--to=mazziesaccount@gmail.com \
--cc=David.Laight@aculab.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=subhajit.ghosh@tweaklogic.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