From: Conor Dooley <conor@kernel.org>
To: peiyu li <579lpy@gmail.com>
Cc: jic23@kernel.org, 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
Subject: Re: [PATCH v2 2/2] dt-bindings: iio: humidity: Add TI HDC302x support
Date: Fri, 24 Nov 2023 12:01:52 +0000 [thread overview]
Message-ID: <20231124-much-screen-ea709763e69b@spud> (raw)
In-Reply-To: <CAELPsEaQZ1a-JO2Vne_MZXWN+nVh7LEw1z_wbHVjiLrKPtd_rQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 644 bytes --]
On Fri, Nov 24, 2023 at 07:38:52PM +0800, peiyu li wrote:
> On Sun, Nov 19, 2023 at 21:41, Conor Dooley wrote：
> ...
> > > - change the maintainers to me.
> > > - hdc3020,hdc3021,hdc3022 are compatible,I've changed the dirver.
> >
> > Does that even compile? It was the binding I wanted you to change, not
> > the driver. Take a look at the example-schema for how to do this.
> In example-schema.yaml, I did not see another way of writing "compatible".
> So does this mean I need to add an example contains
> compatible = "ti,hdc3021", "ti,hdc3020";
There is an example in the example schema with two compatibles, take a
look.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-11-24 12:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-18 10:58 [PATCH v2 1/2] iio: humidity: Add driver for ti HDC302x humidity sensors Li peiyu
2023-11-18 11:02 ` [PATCH v2 2/2] dt-bindings: iio: humidity: Add TI HDC302x support Li peiyu
2023-11-19 13:41 ` Conor Dooley
2023-11-24 11:38 ` peiyu li
2023-11-24 12:01 ` Conor Dooley [this message]
2023-11-20 17:26 ` [PATCH v2 1/2] 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=20231124-much-screen-ea709763e69b@spud \
--to=conor@kernel.org \
--cc=579lpy@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@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