From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Rodrigo Alencar via B4 Relay
<devnull+rodrigo.alencar.analog.com@kernel.org>,
rodrigo.alencar@analog.com, linux-kernel@vger.kernel.org,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-doc@vger.kernel.org, David Lechner <dlechner@baylibre.com>,
Andy Shevchenko <andy@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH v7 2/8] iio: core: add fixed point parsing with 64-bit parts
Date: Mon, 23 Feb 2026 11:06:58 +0200 [thread overview]
Message-ID: <aZwYshRxNgSh3CWk@smile.fi.intel.com> (raw)
In-Reply-To: <20260222172912.60a103c0@jic23-huawei>
On Sun, Feb 22, 2026 at 05:29:12PM +0000, Jonathan Cameron wrote:
> On Mon, 16 Feb 2026 15:02:17 +0000
> Rodrigo Alencar via B4 Relay <devnull+rodrigo.alencar.analog.com@kernel.org> wrote:
>
> > Add iio_str_to_fixpoint64() function that leverages simple_strtoull()
> > to parse numbers from a string.
> > A helper function __iio_str_to_fixpoint64() replaces
> > __iio_str_to_fixpoint() implementation, extending its usage for
> > 64-bit fixed-point parsing.
> >
> > Signed-off-by: Rodrigo Alencar <rodrigo.alencar@analog.com>
> Hi Rodrigo.
>
> This looks fine to me, but given earlier discussions I'd ideally like
> to wait for a final review from Andy.
It all depends on the series from Dmitry Antipov.
Can somebody help reviewing the patch 1 there?
https://lore.kernel.org/linux-hardening/20260212125628.739276-1-dmantipov@yandex.ru/
When it's in, we can continue on this one. TL;DR: for me this is on hold.
But if you see the need to have the driver being in IIO, please add a big
fat FIXME to make sure we will get this all being sorted out in the
(nearest?) future.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-02-23 9:07 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 15:02 [PATCH v7 0/8] ADF41513/ADF41510 PLL frequency synthesizers Rodrigo Alencar
2026-02-16 15:02 ` Rodrigo Alencar via B4 Relay
2026-02-16 15:02 ` [PATCH v7 1/8] dt-bindings: iio: frequency: add adf41513 Rodrigo Alencar
2026-02-16 15:02 ` Rodrigo Alencar via B4 Relay
2026-02-16 15:02 ` [PATCH v7 2/8] iio: core: add fixed point parsing with 64-bit parts Rodrigo Alencar
2026-02-16 15:02 ` Rodrigo Alencar via B4 Relay
2026-02-22 17:29 ` Jonathan Cameron
2026-02-23 9:06 ` Andy Shevchenko [this message]
2026-02-23 10:37 ` Rodrigo Alencar
2026-02-23 10:41 ` Andy Shevchenko
2026-03-01 12:23 ` Jonathan Cameron
2026-03-02 8:27 ` Andy Shevchenko
2026-03-02 9:19 ` Rodrigo Alencar
2026-03-02 9:33 ` Andy Shevchenko
2026-03-02 10:13 ` Rodrigo Alencar
2026-03-02 10:20 ` Andy Shevchenko
2026-02-16 15:02 ` [PATCH v7 3/8] iio: test: add kunit test for fixed-point parsing Rodrigo Alencar
2026-02-16 15:02 ` Rodrigo Alencar via B4 Relay
2026-02-22 17:34 ` Jonathan Cameron
2026-02-16 15:02 ` [PATCH v7 4/8] iio: frequency: adf41513: driver implementation Rodrigo Alencar
2026-02-16 15:02 ` Rodrigo Alencar via B4 Relay
2026-02-16 15:02 ` [PATCH v7 5/8] iio: frequency: adf41513: handle LE synchronization feature Rodrigo Alencar
2026-02-16 15:02 ` Rodrigo Alencar via B4 Relay
2026-02-16 15:02 ` [PATCH v7 6/8] iio: frequency: adf41513: features on frequency change Rodrigo Alencar
2026-02-16 15:02 ` Rodrigo Alencar via B4 Relay
2026-02-16 15:02 ` [PATCH v7 7/8] docs: iio: add documentation for adf41513 driver Rodrigo Alencar
2026-02-16 15:02 ` Rodrigo Alencar via B4 Relay
2026-02-16 15:02 ` [PATCH v7 8/8] Documentation: ABI: testing: add common ABI file for iio/frequency Rodrigo Alencar
2026-02-16 15:02 ` Rodrigo Alencar via B4 Relay
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=aZwYshRxNgSh3CWk@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=devnull+rodrigo.alencar.analog.com@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=rodrigo.alencar@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.