From: Mark Brown <broonie@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Astrid Rost <astrid.rost@axis.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
kernel@axis.com,
alsa-devel-mejlinglistan <alsa-devel@alsa-project.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: sound: ts3a227e: add control of debounce times
Date: Thu, 8 Sep 2022 15:35:15 +0100 [thread overview]
Message-ID: <Yxn9o1MVMPnFO3PM@sirena.org.uk> (raw)
In-Reply-To: <2b81d814-f47a-e548-83dc-b1e38857e8ce@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 578 bytes --]
On Thu, Sep 08, 2022 at 02:20:42PM +0200, Krzysztof Kozlowski wrote:
> Anyway new properties cannot be accepted. This has to be converted to DT
> schema (YAML).
Doing a whole binding conversion feels like a bit of a steep requirement
when people are just adding a simple property, it's a lot of stop energy
to figure out the tooling, do the conversion and deal with all the
bikeshedding that the tools don't catch. It's definitely nice if people
want to look at that, for more complex binding changes it gets more
reasonable but for trivial properties it's disproportionate.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-09-08 14:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 13:58 [PATCH] dt-bindings: sound: ts3a227e: add control of debounce times Astrid Rost
2022-09-08 12:20 ` Krzysztof Kozlowski
2022-09-08 14:35 ` Mark Brown [this message]
2022-09-09 7:16 ` Astrid Rost
2022-09-09 7:25 ` Krzysztof Kozlowski
2022-09-09 7:23 ` Krzysztof Kozlowski
2022-09-09 8:21 ` Krzysztof Kozlowski
2022-09-09 18:47 ` Mark Brown
2022-09-12 7:26 ` Astrid Rost
2022-09-13 7:16 ` Astrid Rost
2022-09-13 9:13 ` 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=Yxn9o1MVMPnFO3PM@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=astrid.rost@axis.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@axis.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lgirdwood@gmail.com \
--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