From: Mark Brown <broonie@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Kiseok Jo <kiseok.jo@irondevice.com>
Subject: Re: [PATCH] ASoC: dt-bindings: Drop broken irondevice,sma1303 binding
Date: Wed, 1 Feb 2023 15:00:55 +0000 [thread overview]
Message-ID: <Y9p+p6wt8WugDBuH@sirena.org.uk> (raw)
In-Reply-To: <6491d6fb-2a10-1c80-d422-8300d5a75ce4@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 692 bytes --]
On Wed, Feb 01, 2023 at 03:43:12PM +0100, Krzysztof Kozlowski wrote:
> I tried. I started writing patch to fix few things in this binding and
> then noticed that it is entirely empty and documents nothing.
I really don't see an empty binding as a major problem in and of itself,
we can always add properties later. Again, I can't tell what the
problems you're seeing are.
> The trouble is that soon you will send it to Linus and then it becomes
> the ABI even though no one ever approved or reviewed the actual ABI.
So send a patch to delete the property parsing code then, like I say
removing the entire driver is very much an overraction. The properties
are all optional in the code.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-02-01 15:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 13:10 Krzysztof Kozlowski
2023-02-01 13:13 ` Krzysztof Kozlowski
2023-02-01 14:03 ` Mark Brown
2023-02-01 14:43 ` Krzysztof Kozlowski
2023-02-01 15:00 ` Mark Brown [this message]
2023-02-02 1:54 ` Ki-Seok Jo
2023-02-02 5:28 ` Ki-Seok Jo
2023-02-02 8:44 ` Krzysztof Kozlowski
2023-02-02 8:58 ` Ki-Seok Jo
2023-02-02 9:03 ` 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=Y9p+p6wt8WugDBuH@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree@vger.kernel.org \
--cc=kiseok.jo@irondevice.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=robh+dt@kernel.org \
--cc=tiwai@suse.com \
/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®