From: Roan van Dijk <roan@protonic.nl>
To: Rob Herring <robh@kernel.org>
Cc: david@protonic.nl, Jonathan Cameron <jic23@kernel.org>,
Tomasz Duszynski <tomasz.duszynski@octakon.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh+dt@kernel.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-iio@vger.kernel.org
Subject: Re: [PATCH v1 1/3] dt-bindings: iio: chemical: sensirion,scd4x: Add yaml description
Date: Tue, 7 Sep 2021 15:13:45 +0200 [thread overview]
Message-ID: <420dc3e5-3bfb-b29f-25bb-bfdadfad9dc2@protonic.nl> (raw)
In-Reply-To: <YTJ8z2RpR0JUo2Yk@robh.at.kernel.org>
On 03-09-2021 21:51, Rob Herring wrote:
> On Wed, 01 Sep 2021 12:59:09 +0200, Roan van Dijk wrote:
>> Add documentation for the SCD4x carbon dioxide sensor from Sensirion.
>>
>> Signed-off-by: Roan van Dijk <roan@protonic.nl>
>> ---
>> .../iio/chemical/sensirion,scd4x.yaml | 46 +++++++++++++++++++
>> 1 file changed, 46 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/iio/chemical/sensirion,scd4x.yaml
>>
> Reviewed-by: Rob Herring <robh@kernel.org>
Sorry, I forgot about this. It will be added to the next patch.
Thanks,
Roan
next prev parent reply other threads:[~2021-09-07 13:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 10:59 [PATCH v1 0/3] iio: chemical: Add support for Sensirion SCD4x CO2 sensor Roan van Dijk
2021-09-01 10:59 ` [PATCH v1 1/3] dt-bindings: iio: chemical: sensirion,scd4x: Add yaml description Roan van Dijk
2021-09-03 19:51 ` Rob Herring
2021-09-07 13:13 ` Roan van Dijk [this message]
2021-09-01 10:59 ` [PATCH v1 2/3] MAINTAINERS: Add myself as maintainer of the scd4x driver Roan van Dijk
2021-09-01 10:59 ` [PATCH v1 3/3] drivers: iio: chemical: Add support for Sensirion SCD4x CO2 sensor Roan van Dijk
[not found] ` <20210905152253.3ea6beb3@jic23-huawei>
[not found] ` <7b93a51a-3856-63a8-20fb-e2b7f341254a@protonic.nl>
2021-09-08 17:08 ` Jonathan Cameron
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=420dc3e5-3bfb-b29f-25bb-bfdadfad9dc2@protonic.nl \
--to=roan@protonic.nl \
--cc=david@protonic.nl \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=tomasz.duszynski@octakon.com \
/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).