From: Jonathan Cameron <jic23@kernel.org>
To: Marcus Folkesson <marcus.folkesson@gmail.com>
Cc: Kent Gustavsson <kent@minoris.se>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Cosmin Tanislav <demonsingur@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
ChiYuan Huang <cy_huang@richtek.com>,
Haibo Chen <haibo.chen@nxp.com>,
Ramona Bolboaca <ramona.bolboaca@analog.com>,
Ibrahim Tilki <Ibrahim.Tilki@analog.com>,
ChiaEn Wu <chiaen_wu@richtek.com>,
William Breathitt Gray <william.gray@linaro.org>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 0/6] Add support for the whole MCP39xx family
Date: Sun, 27 Aug 2023 19:27:01 +0100 [thread overview]
Message-ID: <20230827192701.30bfd1be@jic23-huawei> (raw)
In-Reply-To: <20230822192259.1125792-1-marcus.folkesson@gmail.com>
On Tue, 22 Aug 2023 21:22:53 +0200
Marcus Folkesson <marcus.folkesson@gmail.com> wrote:
> The main goal with this patchset is to add support for all similar
> MCP39xx ADC chips.
> During all patch iterations we ended up with a few cleanup patches.
>
> See version notes in each patch.
>
> Marcus Folkesson (6):
> dt-bindings: iio: adc: mcp3911: add support for the whole MCP39xx
> family
> iio: adc: mcp3911: make use of dev_err_probe()
> iio: adc: mcp3911: simplify usage of spi->dev
> iio: adc: mcp3911: fix indentation
> iio: adc: mcp3911: avoid ambiguity parameters in macros
> iio: adc: mcp3911: add support for the whole MCP39xx family
>
> .../bindings/iio/adc/microchip,mcp3911.yaml | 6 +
> drivers/iio/adc/Kconfig | 6 +-
> drivers/iio/adc/mcp3911.c | 562 ++++++++++++++----
> 3 files changed, 462 insertions(+), 112 deletions(-)
>
>
> base-commit: b320441c04c9bea76cbee1196ae55c20288fd7a6
Series applied.
Thanks to both Marcus (for working through the iterations) and Andy for
providing the detailed feedback.
Jonathan
prev parent reply other threads:[~2023-08-27 18:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 19:22 [PATCH v8 0/6] Add support for the whole MCP39xx family Marcus Folkesson
2023-08-22 19:22 ` [PATCH v8 1/6] dt-bindings: iio: adc: mcp3911: add " Marcus Folkesson
2023-08-22 19:22 ` [PATCH v8 2/6] iio: adc: mcp3911: make use of dev_err_probe() Marcus Folkesson
2023-08-22 19:22 ` [PATCH v8 3/6] iio: adc: mcp3911: simplify usage of spi->dev Marcus Folkesson
2023-08-22 19:22 ` [PATCH v8 4/6] iio: adc: mcp3911: fix indentation Marcus Folkesson
2023-08-22 19:22 ` [PATCH v8 5/6] iio: adc: mcp3911: avoid ambiguity parameters in macros Marcus Folkesson
2023-08-22 19:22 ` [PATCH v8 6/6] iio: adc: mcp3911: add support for the whole MCP39xx family Marcus Folkesson
2023-08-22 19:47 ` Marcus Folkesson
2023-08-27 18:27 ` 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=20230827192701.30bfd1be@jic23-huawei \
--to=jic23@kernel.org \
--cc=Ibrahim.Tilki@analog.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=chiaen_wu@richtek.com \
--cc=conor+dt@kernel.org \
--cc=cy_huang@richtek.com \
--cc=demonsingur@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=haibo.chen@nxp.com \
--cc=kent@minoris.se \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcus.folkesson@gmail.com \
--cc=ramona.bolboaca@analog.com \
--cc=robh+dt@kernel.org \
--cc=william.gray@linaro.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;
as well as URLs for NNTP newsgroup(s).