From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Jonathan Cameron <jic23@kernel.org>
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] iio: adc: ad7124: Implement input validation
Date: Mon, 18 Nov 2024 12:19:54 +0100 [thread overview]
Message-ID: <cover.1731404695.git.u.kleine-koenig@baylibre.com> (raw)
Hello,
(implicit) v1 of the series can be found at
https://lore.kernel.org/linux-iio/20241108181813.272593-4-u.kleine-koenig@baylibre.com.
This v2 bases on v6.12-rc1 + commit 64612ec9b909 ("iio: adc: ad7124:
Disable all channels at probe time") which is already in next.
Changes since v1:
- reword commit log of patch #1 to honestly tell that the maximal
number of logical channels is a limitation of the current driver
implementation (and not one imposed by hardware).
- Make the driver explicitly fail to load if > 16 channels are defined.
v1 only limited the maximal channel address which then later yielded
a probe failure on the first channel exeeding that maximum.
- in patch #2 fix "passing zero to 'dev_err_probe'" as reported by
smatch + Dan Carpenter.
- Fix my address in patch #2's S-o-b trailer.
Uwe Kleine-König (2):
iio: adc: ad7124: Don't create more channels than the driver can
handle
iio: adc: ad7124: Refuse invalid input specifiers
drivers/iio/adc/ad7124.c | 28 ++++++++++++++++++++++++++++
1 file changed, 28 insertions(+)
base-commit: 9852d85ec9d492ebef56dc5f229416c925758edc
prerequisite-patch-id: 617af17fc377a984762c61893b9f2a92ae62213a
--
2.45.2
next reply other threads:[~2024-11-18 11:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 11:19 Uwe Kleine-König [this message]
2024-11-18 11:19 ` [PATCH v2 1/2] iio: adc: ad7124: Don't create more channels than the driver can handle Uwe Kleine-König
2024-11-18 11:19 ` [PATCH v2 2/2] iio: adc: ad7124: Refuse invalid input specifiers Uwe Kleine-König
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=cover.1731404695.git.u.kleine-koenig@baylibre.com \
--to=u.kleine-koenig@baylibre.com \
--cc=Michael.Hennerich@analog.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®