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 v2 1/5] dt-bindings: iio: pressure: bmp085: Add BMP380 compatible string
Date: Mon, 04 Jul 2022 11:26:17 +0200 [thread overview]
Message-ID: <9a07f9b011646284db9e2eeeb76b80afad599b68.camel@gmail.com> (raw)
In-Reply-To: <ad00b52e-cead-920a-9b99-db4032cb6d0c@linaro.org>
On lun, 2022-07-04 at 10:58 +0200, Krzysztof Kozlowski wrote:
> On 04/07/2022 02:26, Angel Iglesias wrote:
> > Add bosch,bmp380 compatible string for the new family of sensors.
> > This family includes the BMP380, BMP384 and BMP388. The register
> > map
> > in this family changes substantially and introduces new features
> > but core concepts and operations carryover from the previous
> > iterations
> >
> > Signed-off-by: Angel Iglesias <ang.iglesiasg@gmail.com>
>
> Please add Acked-by/Reviewed-by tags when posting new versions.
> However,
> there's no need to repost patches *only* to add the tags. The
> upstream
> maintainer will do that for acks received on the version they apply.
>
> https://elixir.bootlin.com/linux/v5.17/source/Documentation/process/submitting-patches.rst#L540
>
> If a tag was not added on purpose, please state why and what changed.
>
> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>
>
> Best regards,
> Krzysztof
Apologies for the inconvenience. I'll be more careful with kernel
protocol and use the proper tags. Thank you for your time.
Kind regards,
Angel
prev parent reply other threads:[~2022-07-04 9:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 0:26 [PATCH v2 1/5] dt-bindings: iio: pressure: bmp085: Add BMP380 compatible string Angel Iglesias
2022-07-04 8:58 ` Krzysztof Kozlowski
2022-07-04 9:26 ` 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=9a07f9b011646284db9e2eeeb76b80afad599b68.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).