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: Fri, 9 Sep 2022 19:47:39 +0100 [thread overview]
Message-ID: <YxuKS7S3/aHtDNMq@sirena.org.uk> (raw)
In-Reply-To: <9a72bd22-9298-65ce-a894-540f98745a7e@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 974 bytes --]
On Fri, Sep 09, 2022 at 10:21:30AM +0200, Krzysztof Kozlowski wrote:
> It's more than one property and many other patch submitters were using
> this reason as well. As a result, few TXT bindings grew from 5 to 10
> properties within one year and there was still no conversion to YAML.
> I understand your concerns however I have stronger motivation to do the
> conversion, than for accepting new features.
For me the metric is proportionality - the amount of extra effort we're
forcing people to go through should bear some relationship to the change
they're trying to make. We can't very well complain that people don't
upstream things if when they try to do so they have to jump through some
tangentially related hoops relating to the existing code in order to get
anything done. We can and should *ask* people to do additional cleanups
or whatever but creating requirements that dramatically expand the scope
of work someone's having to do are a lot of stop energy.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-09-09 18:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 13:58 Astrid Rost
2022-09-08 12:20 ` Krzysztof Kozlowski
2022-09-08 14:35 ` Mark Brown
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 [this message]
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=YxuKS7S3/aHtDNMq@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
all inboxes | Powered by JetHome®