public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
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 v4 4/4] iio: humidity: Add TI HDC302x support
Date: Wed, 6 Dec 2023 14:53:29 +0000	[thread overview]
Message-ID: <20231206-quarrel-dill-27b94d881ec0@spud> (raw)
In-Reply-To: <20231206135148.559564-1-579lpy@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 397 bytes --]

On Wed, Dec 06, 2023 at 09:51:48PM +0800, Li peiyu wrote:
> Add device tree bindings for HDC3020/HDC3021/HDC3022 humidity and
> temperature sensors.
> 
> Signed-off-by: Li peiyu <579lpy@gmail.com>

If there is a resubmission, please prepend "dt-bindings: " to your
commit $subject. Otherwise, I am only with this.
Reviewed-by: Conor Dooley <conor.dooley@microchip.com>

Thanks,
Conor.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2023-12-06 14:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-06 13:46 [PATCH v4 0/4] iio: humidity: Add driver for ti HDC302x humidity sensors Li peiyu
2023-12-06 13:48 ` [PATCH v4 1/4] iio: core: introduce trough modifier for minimum values Li peiyu
2023-12-06 17:52   ` Jonathan Cameron
2023-12-06 13:49 ` [PATCH v4 2/4] iio: ABI: document temperature and humidity peak/trough raw attributes Li peiyu
2023-12-06 13:51 ` [PATCH v4 3/4] iio: humidity: Add driver for ti HDC302x humidity sensors Li peiyu
2023-12-06 18:00   ` Jonathan Cameron
2023-12-06 13:51 ` [PATCH v4 4/4] iio: humidity: Add TI HDC302x support Li peiyu
2023-12-06 14:53   ` Conor Dooley [this message]
2023-12-06 18:42   ` Krzysztof Kozlowski
2023-12-11 10:37     ` peiyu li
2023-12-11 10:46       ` Krzysztof Kozlowski

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=20231206-quarrel-dill-27b94d881ec0@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