From: Jonathan Cameron <jic23@kernel.org>
To: Kaustabh Chakraborty <kauschluss@disroot.org>
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
conor+dt@kernel.org
Subject: Re: [PATCH 3/3] dt-bindings: iio: light: stk33xx: add compatible for stk3013
Date: Sat, 13 Jul 2024 13:06:20 +0100 [thread overview]
Message-ID: <20240713130620.79d47130@jic23-huawei> (raw)
In-Reply-To: <20240712152417.97726-3-kauschluss@disroot.org>
On Fri, 12 Jul 2024 20:54:02 +0530
Kaustabh Chakraborty <kauschluss@disroot.org> wrote:
> Add the compatible string of stk3013 to the existing list.
Should include how this differs from existing devices such that it doesn't
make sense to use a fallback compatible.
>
> Signed-off-by: Kaustabh Chakraborty <kauschluss@disroot.org>
> ---
> Documentation/devicetree/bindings/iio/light/stk33xx.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/iio/light/stk33xx.yaml b/Documentation/devicetree/bindings/iio/light/stk33xx.yaml
> index f6e22dc9814a..6003da66a7e6 100644
> --- a/Documentation/devicetree/bindings/iio/light/stk33xx.yaml
> +++ b/Documentation/devicetree/bindings/iio/light/stk33xx.yaml
> @@ -19,6 +19,7 @@ allOf:
> properties:
> compatible:
> enum:
> + - sensortek,stk3013
> - sensortek,stk3310
> - sensortek,stk3311
> - sensortek,stk3335
next prev parent reply other threads:[~2024-07-13 12:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 15:24 [PATCH 1/3] iio: light: stk3310: relax chipid check warning Kaustabh Chakraborty
2024-07-12 15:24 ` [PATCH 2/3] iio: light: stk3310: add support for stk3013 Kaustabh Chakraborty
2024-07-12 15:24 ` [PATCH 3/3] dt-bindings: iio: light: stk33xx: add compatible " Kaustabh Chakraborty
2024-07-13 12:06 ` Jonathan Cameron [this message]
2024-07-15 20:02 ` Kaustabh Chakraborty
2024-07-16 16:43 ` Jonathan Cameron
2024-07-17 15:58 ` Kaustabh Chakraborty
2024-07-20 12:45 ` Jonathan Cameron
2024-07-13 12:06 ` [PATCH 1/3] iio: light: stk3310: relax chipid check warning Jonathan Cameron
2024-07-14 8:51 ` Kaustabh Chakraborty
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=20240713130620.79d47130@jic23-huawei \
--to=jic23@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kauschluss@disroot.org \
--cc=linux-iio@vger.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