From: Conor Dooley <conor@kernel.org>
To: Li peiyu <579lpy@gmail.com>
Cc: jic23@kernel.org, javier.carrasco.cruz@gmail.com,
lars@metafoo.de, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 4/4] dt-bindings: iio: humidity: Add TI HDC302x support
Date: Mon, 11 Dec 2023 18:21:12 +0000 [thread overview]
Message-ID: <20231211-tackiness-imprecise-685882c9c318@spud> (raw)
In-Reply-To: <20231211123101.9868-1-579lpy@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 281 bytes --]
On Mon, Dec 11, 2023 at 08:31:01PM +0800, Li peiyu wrote:
> Add device tree bindings for HDC3020/HDC3021/HDC3022 humidity and
> temperature sensors.
>
> Signed-off-by: Li peiyu <579lpy@gmail.com>
Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
Cheers,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-12-11 18:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 12:22 [PATCH v6 0/4] iio: humidity: Add driver for ti HDC302x humidity sensors Li peiyu
2023-12-11 12:27 ` [PATCH v6 1/4] iio: core: introduce trough info element for minimum values Li peiyu
2023-12-11 12:28 ` [PATCH v6 2/4] iio: ABI: document temperature and humidity peak/trough raw attributes Li peiyu
2023-12-11 12:29 ` [PATCH v6 3/4] iio: humidity: Add driver for ti HDC302x humidity sensors Li peiyu
2024-01-20 4:17 ` Lars-Peter Clausen
2024-01-20 16:14 ` Javier Carrasco
2024-01-21 13:51 ` Jonathan Cameron
2023-12-11 12:31 ` [PATCH v6 4/4] dt-bindings: iio: humidity: Add TI HDC302x support Li peiyu
2023-12-11 18:21 ` Conor Dooley [this message]
2023-12-11 19:39 ` [PATCH v6 0/4] iio: humidity: Add driver for ti HDC302x humidity sensors 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=20231211-tackiness-imprecise-685882c9c318@spud \
--to=conor@kernel.org \
--cc=579lpy@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=javier.carrasco.cruz@gmail.com \
--cc=jic23@kernel.org \
--cc=krzysztof.kozlowski+dt@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