From: Jonathan Cameron <jic23@kernel.org>
To: Salih Erim <salih.erim@amd.com>
Cc: Guilherme Ivo Bozi <guilherme.bozi@usp.br>,
anand.ashok.dumbre@xilinx.com, andy@kernel.org,
conall.ogriofa@amd.com, dlechner@baylibre.com,
manish.narani@xilinx.com, michal.simek@amd.com,
nuno.sa@analog.com, Jonathan.Cameron@huawei.com,
linux-arm-kernel@lists.infradead.org, linux-iio@vger.kernel.org
Subject: Re: [PATCH v4 0/3] iio: adc: xilinx-ams: refactor alarm handling to table-driven design
Date: Sat, 16 May 2026 13:29:02 +0100 [thread overview]
Message-ID: <20260516132902.30edeaa7@jic23-huawei> (raw)
In-Reply-To: <0ae1a3d0-cc51-4d5f-997c-04d3114121ca@amd.com>
On Thu, 14 May 2026 02:21:37 +0100
Salih Erim <salih.erim@amd.com> wrote:
> Hi,
>
> On 5/13/2026 1:31 AM, Guilherme Ivo Bozi wrote:
>
> > v3 -> v4:
> > - Removed unnecessary 'event < 0' check for type e32
>
> Thanks for addressing the feedback.
> Tested on ZCU102 Rev1.0. Driver probes successfully with no errors.
>
> For the series:
> Reviewed-by: Salih Erim <salih.erim@amd.com>
> Tested-by: Salih Erim <salih.erim@amd.com>
>
Given I think the 1st patch is a defensive fix rather than one we
actually expect to ever see (and I don't want to delay the other two),
I've applied the whole series to the testing branch of iio.git.
Once I've caught up with the review backlog and the bots have finished
playing with it, I'll push that out as togreg which gets picked up for
linux-next.
Thanks,
Jonathan
> Salih
>
prev parent reply other threads:[~2026-05-16 12:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 0:31 [PATCH v4 0/3] iio: adc: xilinx-ams: refactor alarm handling to table-driven design Guilherme Ivo Bozi
2026-05-13 0:31 ` [PATCH v4 1/3] iio: adc: xilinx-ams: fix out-of-bounds channel lookup in event handling Guilherme Ivo Bozi
2026-05-13 0:31 ` [PATCH v4 2/3] iio: adc: xilinx-ams: use guard(mutex) for automatic locking Guilherme Ivo Bozi
2026-05-13 0:31 ` [PATCH v4 3/3] iio: adc: xilinx-ams: refactor alarm mapping to table-driven approach Guilherme Ivo Bozi
2026-05-14 1:21 ` [PATCH v4 0/3] iio: adc: xilinx-ams: refactor alarm handling to table-driven design Salih Erim
2026-05-16 12:29 ` Jonathan Cameron [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=20260516132902.30edeaa7@jic23-huawei \
--to=jic23@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=anand.ashok.dumbre@xilinx.com \
--cc=andy@kernel.org \
--cc=conall.ogriofa@amd.com \
--cc=dlechner@baylibre.com \
--cc=guilherme.bozi@usp.br \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=manish.narani@xilinx.com \
--cc=michal.simek@amd.com \
--cc=nuno.sa@analog.com \
--cc=salih.erim@amd.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