From: Angel Iglesias <ang.iglesiasg@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
linux-iio@vger.kernel.org
Cc: Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Andreas Klinger <ak@it-klinger.de>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/5] dt-bindings: iio: pressure: bmp085: Add BMP580 compatible string
Date: Mon, 26 Dec 2022 13:43:08 +0100 [thread overview]
Message-ID: <9ba1d5781ee43096c2660799321b43184e9a0c76.camel@gmail.com> (raw)
In-Reply-To: <6b533031-e46c-3c7a-9d7b-3118c5ab7219@linaro.org>
On Mon, 2022-12-26 at 13:05 +0100, Krzysztof Kozlowski wrote:
> On 25/12/2022 17:59, Angel Iglesias wrote:
> > Add bosch,bmp580 to compatible string for the new family of sensors.
> > This family includes the BMP580 and BMP581 sensors. The register map
> > in this family presents significant departures from previous generations.
> >
> > Signed-off-by: Angel Iglesias <ang.iglesiasg@gmail.com>
>
> I did not receive anything else - no cover letter, no rest of patches -
> so difficult to judge whether driver is implemented the same way.
Sorry about that. I'll need to send an updated version with a few corrections.
I'll be sure next time to send the complete patchset your way.
Thanks for your time!
> For this patch only, assuming it matches the driver:
>
> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>
> Best regards,
> Krzysztof
>
prev parent reply other threads:[~2022-12-26 12:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1671986815.git.ang.iglesiasg@gmail.com>
2022-12-25 16:59 ` [PATCH 4/5] dt-bindings: iio: pressure: bmp085: Add BMP580 compatible string Angel Iglesias
2022-12-26 12:05 ` Krzysztof Kozlowski
2022-12-26 12:43 ` Angel Iglesias [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=9ba1d5781ee43096c2660799321b43184e9a0c76.camel@gmail.com \
--to=ang.iglesiasg@gmail.com \
--cc=ak@it-klinger.de \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--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=robh+dt@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).