From: David Lechner <dlechner@baylibre.com>
To: Jakub Szczudlo <jakubszczudlo40@gmail.com>, linux-iio@vger.kernel.org
Cc: jic23@kernel.org, nuno.sa@analog.com, andy@kernel.org,
marcelo.schmitt@analog.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, mike.looijmans@topic.nl,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
jorge.marques@analog.com, antoniu.miclaus@analog.com,
mazziesaccount@gmail.com, jishnu.prakash@oss.qualcomm.com,
duje@dujemihanovic.xyz, wens@kernel.org,
sakari.ailus@linux.intel.com, linusw@kernel.org
Subject: Re: [PATCH 0/3] iio: adc: Extend ti-ads1100 driver
Date: Tue, 9 Jun 2026 11:10:02 -0500 [thread overview]
Message-ID: <6305149b-d334-491f-85c2-085fe42cae98@baylibre.com> (raw)
In-Reply-To: <20260607183542.368184-1-jakubszczudlo40@gmail.com>
On 6/7/26 1:35 PM, Jakub Szczudlo wrote:
> Extend ADS 1100 driver to support ADS1110, which is a pin-to-pin
> compatible device with higher resolution. This patch also updates the
> device tree bindings and Kconfig description to reflect the new
> supported device.
>
> Signed-off-by: jszczudlo <jakubszczudlo40@gmail.com>
> ---
> jszczudlo (3):
> dt-bindings: iio: adc: Update title and enum
> iio: adc: Update Kconfig description for TI_ADS1100
> iio: adc: Add ti-ads1110 support to ti-ads1100 driver
>
> .../bindings/iio/adc/ti,ads1100.yaml | 3 +-
> drivers/iio/adc/Kconfig | 6 +-
> drivers/iio/adc/ti-ads1100.c | 165 +++++++++++++-----
> 3 files changed, 131 insertions(+), 43 deletions(-)
>
I assume this is v2 of [1]? the subject should include [PATCH v2] and the
cover letter should include a changelog. See [2].
[1]: https://lore.kernel.org/linux-iio/20260527164312.355729-1-jakubszczudlo40@gmail.com/
[2]: https://www.kernel.org/doc/html/latest/process/submitting-patches.html
next prev parent reply other threads:[~2026-06-09 16:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-07 18:35 [PATCH 0/3] iio: adc: Extend ti-ads1100 driver Jakub Szczudlo
2026-06-07 18:35 ` [PATCH 1/3] dt-bindings: iio: adc: Update title and enum Jakub Szczudlo
2026-06-08 17:30 ` Conor Dooley
2026-06-08 17:57 ` Jonathan Cameron
2026-06-07 18:35 ` [PATCH 2/3] iio: adc: Update Kconfig description for TI_ADS1100 Jakub Szczudlo
2026-06-08 6:45 ` Joshua Crofts
2026-06-08 11:43 ` Andy Shevchenko
2026-06-08 17:53 ` Jonathan Cameron
2026-06-07 18:35 ` [PATCH 3/3] iio: adc: Add ti-ads1110 support to ti-ads1100 driver Jakub Szczudlo
2026-06-07 18:50 ` sashiko-bot
2026-06-08 7:39 ` Joshua Crofts
2026-06-08 18:03 ` Jonathan Cameron
2026-06-08 18:23 ` Jonathan Cameron
2026-06-08 6:42 ` [PATCH 0/3] iio: adc: Extend " Joshua Crofts
2026-06-08 11:42 ` Andy Shevchenko
2026-06-08 18:25 ` Jonathan Cameron
2026-06-09 16:10 ` David Lechner [this message]
2026-06-13 14:44 ` Jakub Szczudło
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=6305149b-d334-491f-85c2-085fe42cae98@baylibre.com \
--to=dlechner@baylibre.com \
--cc=andy@kernel.org \
--cc=antoniu.miclaus@analog.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=duje@dujemihanovic.xyz \
--cc=jakubszczudlo40@gmail.com \
--cc=jic23@kernel.org \
--cc=jishnu.prakash@oss.qualcomm.com \
--cc=jorge.marques@analog.com \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.schmitt@analog.com \
--cc=mazziesaccount@gmail.com \
--cc=mike.looijmans@topic.nl \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=wens@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