devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Ben Collins <bcollins@watter.com>
Cc: "David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Andrew Hepp" <andrew.hepp@ahepp.dev>,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
	"Andy Shevchenko" <andy@kernel.org>
Subject: Re: [PATCH v8 0/5] iio: mcp9600: Features and improvements
Date: Mon, 25 Aug 2025 10:38:47 +0100	[thread overview]
Message-ID: <20250825103740.31ed77c8@jic23-huawei> (raw)
In-Reply-To: <20250822-upstream-changes-v8-0-40bb1739e3e2@watter.com>

On Fri, 22 Aug 2025 09:23:49 -0400
Ben Collins <bcollins@watter.com> wrote:

Series applied with that unnecessary include that David pointed out dropped.

Applied to the togreg branch of iio.git but initially pushed out as testing
to give 0-day a few days to poke at it.

Thanks,

Jonathan


> ChangeLog:
> v7 -> v8:
>   - Style changes in dt-bindings example
>   - Simplify some return value checks
>   - Move assignment to where it's checked
>   - Speeling
> 
> v6 -> v7:
>   - Separate out the mcp9600 IIR series into its own series as there is
>     a lot of conversation around implementation (removed related
>     comments from this changelog).
> 
> v5 -> v6:
>   - Fix accidental typo added in dt-bindings: IRQ_TYPE_EDGE_RISIN
>   - Correct some constraints in dt-bindings
>   - Reverse if/then for mcp9601 vs mcp9600 constraints in dt-bindings
>   - Updates to changelog for patch 2/6 (dt-bindings mcp9600)
>   - Cleanup tabs that were converted to spaces
>   - Split thermocouple-type default to separate patch
> 
> v4 -> v5:
>   - None
> 
> v3 -> v4:
>   - Based on feedback from David Lechner <dlechner@baylibre.com>
>     * Allow fallback compatible in dt-bindings for mcp9601.
>   - Based on feedback from Jonathan Cameron <jic23@kernel.org>
>     * Be explicit in patch description for fixed width changes.
>     * Check chip_info for NULL to quiet warnings from kernel-test-robot
>     * Remove "and similar" for long description of MCP9600.
>   - Set default 3 for thermocouple in dt-binding
>   - Rework open/short circuit in dt-bindings
> 
> v2 -> v3:
>   - Improve changelogs in each patch
>   - Based on feedback from Andy Shevchenko <andy.shevchenko@gmail.com>
>     * Set register offsets to fixed width
>     * Fix typos
>     * Future-proof Kconfig changes
>     * Convert to using chip_info paradigm
>     * Verbiage: dt -> firmware description
>     * Use proper specifiers and drop castings
>     * Fix register offset to be fixed-width
>     * u8 for cfg var
>     * Fix % type for u32 to be %u
>     * Make blank lines consistent between case statements
> 
> v1 -> v2:
>   - Break into individual patches
> 
> v1:
>   - Initial patch to enable IIR and thermocouple-type
>   - Recognize mcp9601
> 
> Signed-off-by: Ben Collins <bcollins@watter.com>
> ---
> - Link to v7: https://lore.kernel.org/r/20250819-upstream-changes-v7-0-88a33aa78f6a@watter.com
> 
> ---
> Ben Collins (5):
>       dt-bindings: iio: mcp9600: Set default 3 for thermocouple-type
>       dt-bindings: iio: mcp9600: Add microchip,mcp9601 and add constraints
>       iio: mcp9600: White space and fixed width cleanup
>       iio: mcp9600: Recognize chip id for mcp9601
>       iio: mcp9600: Add support for thermocouple-type
> 
>  .../iio/temperature/microchip,mcp9600.yaml         |  57 +++++++-
>  drivers/iio/temperature/Kconfig                    |   8 +-
>  drivers/iio/temperature/mcp9600.c                  | 151 +++++++++++++++++----
>  3 files changed, 187 insertions(+), 29 deletions(-)
> ---
> base-commit: c17b750b3ad9f45f2b6f7e6f7f4679844244f0b9
> change-id: 20250819-upstream-changes-c89af86743fa
> 
> Best regards,


  parent reply	other threads:[~2025-08-25  9:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-22 13:23 [PATCH v8 0/5] iio: mcp9600: Features and improvements Ben Collins
2025-08-22 13:23 ` [PATCH v8 1/5] dt-bindings: iio: mcp9600: Set default 3 for thermocouple-type Ben Collins
2025-08-23 16:06   ` David Lechner
2025-08-22 13:23 ` [PATCH v8 2/5] dt-bindings: iio: mcp9600: Add microchip,mcp9601 and add constraints Ben Collins
2025-08-23 16:06   ` David Lechner
2025-08-23 16:09     ` David Lechner
2025-08-22 13:23 ` [PATCH v8 3/5] iio: mcp9600: White space and fixed width cleanup Ben Collins
2025-08-22 13:23 ` [PATCH v8 4/5] iio: mcp9600: Recognize chip id for mcp9601 Ben Collins
2025-08-22 15:57   ` Andy Shevchenko
2025-08-22 16:06     ` Ben Collins
2025-08-22 16:47       ` Andy Shevchenko
2025-08-25  9:36         ` Jonathan Cameron
2025-08-22 13:23 ` [PATCH v8 5/5] iio: mcp9600: Add support for thermocouple-type Ben Collins
2025-08-25  9:38 ` Jonathan Cameron [this message]
2025-08-25 10:04   ` [PATCH v8 0/5] iio: mcp9600: Features and improvements Ben Collins

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=20250825103740.31ed77c8@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andrew.hepp@ahepp.dev \
    --cc=andy@kernel.org \
    --cc=bcollins@watter.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=robh@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;
as well as URLs for NNTP newsgroup(s).