From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Archit Anant <architanant5@gmail.com>
Cc: jic23@kernel.org, lars@metafoo.de, Michael.Hennerich@analog.com,
gregkh@linuxfoundation.org, dlechner@baylibre.com,
nuno.sa@analog.com, andy@kernel.org, linux-iio@vger.kernel.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: iio: impedance-analyzer: ad5933: use div64_ul() instead of do_div()
Date: Tue, 17 Feb 2026 10:29:21 +0200 [thread overview]
Message-ID: <aZQm4QH_svsQuaRp@smile.fi.intel.com> (raw)
In-Reply-To: <CADJHxWDCer97pMNHV-69B9AEVY0NfimTcxo8k8yFBbstg0wMQw@mail.gmail.com>
On Mon, Feb 16, 2026 at 09:22:32PM +0530, Archit Anant wrote:
> Gentle ping on this.
>
> Has anyone from AD had a chance to confirm whether the original
> truncation via (mclk / 4) was intentional?
>
> If there are no objections, I can prepare a v2 using the BIT_ULL(29)
> form as suggested.
Gentle ping on reading and understanding the given comments, please!
> On Thu, Jan 22, 2026 at 11:33 PM Andy Shevchenko
> <andriy.shevchenko@intel.com> wrote:
> >
> > On Thu, Jan 22, 2026 at 10:27:52PM +0530, Archit Anant wrote:
> > > (Resending to the list, apologies for the private reply earlier.)
> >
> > First of all, do no top post!
^^^ Have you understood this?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-02-17 8:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 14:56 [PATCH] staging: iio: impedance-analyzer: ad5933: use div64_ul() instead of do_div() Archit Anant
2026-01-22 15:12 ` Andy Shevchenko
2026-01-22 15:15 ` Andy Shevchenko
[not found] ` <CADJHxWB3b+bH2+HBP+SG0jxhGNcozstBeWeDH_3dgS-4c2G-6g@mail.gmail.com>
2026-01-22 18:03 ` Andy Shevchenko
2026-02-16 15:52 ` Archit Anant
2026-02-16 19:02 ` David Lechner
2026-02-16 19:04 ` David Lechner
2026-02-17 16:46 ` Archit Anant
2026-02-18 18:19 ` Jonathan Cameron
2026-02-18 18:36 ` Archit Anant
2026-02-17 8:29 ` Andy Shevchenko [this message]
2026-02-17 16:31 ` Archit Anant
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=aZQm4QH_svsQuaRp@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=architanant5@gmail.com \
--cc=dlechner@baylibre.com \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=nuno.sa@analog.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