From: Joshua Crofts <joshua.crofts1@gmail.com>
To: Chang Yu <marcus.yu.56@gmail.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Shi Hao" <i.shihao.999@gmail.com>,
"Jose A. Perez de Azpillaga" <azpijr@gmail.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 1/2] dt-bindings: iio: light: add as7343
Date: Thu, 15 Oct 2026 09:41:54 +0200 [thread overview]
Message-ID: <20261015094154.0000506c@gmail.com> (raw)
In-Reply-To: <as5LCasyTFjTNL0x@zephyrus-g14.localdomain>
On Tue, 13 Oct 2026 23:15:21 +0800
Chang Yu <marcus.yu.56@gmail.com> wrote:
> > Should be unevaluatedProperties as you're using $refs in the binding,
> > but Jonathan could tweak that when applying.
> >
> There was a discussion about this back in v2 in which Conor was suggesting
> keeping additionalProperties: false if I recall. I don't know the exact
> pros vs cons so I'll defer to the experts here.
Fair enough, if dt maintainers say so then it's fine.
--
Kind regards,
Joshua Crofts
next prev parent reply other threads:[~2026-10-15 7:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 11:56 [PATCH v6 0/2] Add support for AS7343 multi-spectral sensor Chang Yu
2026-10-13 11:56 ` [PATCH v6 1/2] dt-bindings: iio: light: add as7343 Chang Yu
2026-10-13 12:04 ` sashiko-bot
2026-10-13 12:36 ` Joshua Crofts
2026-10-13 15:15 ` Chang Yu
2026-10-15 7:41 ` Joshua Crofts [this message]
2026-10-13 21:23 ` Jose A. Perez de Azpillaga
2026-10-14 11:22 ` Krzysztof Kozlowski
2026-10-13 11:56 ` [PATCH v6 2/2] iio: light: add AS7343 multi-spectral sensor driver Chang Yu
2026-10-13 12:35 ` Joshua Crofts
2026-10-13 16:28 ` Andy Shevchenko
2026-10-13 16:27 ` Andy Shevchenko
2026-10-14 3:17 ` Chang Yu
2026-10-14 10:38 ` Andy Shevchenko
2026-10-14 10:04 ` Jose A. Perez de Azpillaga
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=20261015094154.0000506c@gmail.com \
--to=joshua.crofts1@gmail.com \
--cc=andy@kernel.org \
--cc=azpijr@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=i.shihao.999@gmail.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcus.yu.56@gmail.com \
--cc=nuno.sa@analog.com \
--cc=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.