From: Jonathan Cameron <jic23@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Javier Carrasco <javier.carrasco.cruz@gmail.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Matt Ranostay <matt@ranostay.sg>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: iio: health: maxim,max30102: add max30101
Date: Mon, 25 Mar 2024 20:25:51 +0000 [thread overview]
Message-ID: <20240325202551.08a8a877@jic23-huawei> (raw)
In-Reply-To: <b37af0e0-c707-48e0-980d-4866b9a662db@linaro.org>
On Mon, 25 Mar 2024 13:18:14 +0100
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> wrote:
> On 24/03/2024 20:20, Javier Carrasco wrote:
> > The Maxim max30101 is the replacement for the max30105, which is no
> > longer recommended for future designs.
> >
> > The max30101 does not require new properties, and it can be described
> > with the existing ones for the max30105, which will be used as a
> > fallback compatible.
> >
> > Signed-off-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>
> > ---
> > .../devicetree/bindings/iio/health/maxim,max30102.yaml | 12 ++++++++----
> > 1 file changed, 8 insertions(+), 4 deletions(-)
>
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>
> Best regards,
> Krzysztof
>
>
Thanks,
Series applied to the togreg branch of iio.git and initially pushed out
as testing to get it some build testing from 0-day.
Thanks,
Jonathan
next prev parent reply other threads:[~2024-03-25 20:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-24 19:20 [PATCH v2 0/2] iio: health: max30102: add support for max30101 Javier Carrasco
2024-03-24 19:20 ` [PATCH v2 1/2] dt-bindings: iio: health: maxim,max30102: add max30101 Javier Carrasco
2024-03-25 12:18 ` Krzysztof Kozlowski
2024-03-25 20:25 ` Jonathan Cameron [this message]
2024-03-24 19:20 ` [PATCH v2 2/2] iio: health: max30102: add support for max30101 Javier Carrasco
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=20240325202551.08a8a877@jic23-huawei \
--to=jic23@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=javier.carrasco.cruz@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@ranostay.sg \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).