From: Krzysztof Kozlowski <krzk@kernel.org>
To: Manish Baing <manishbaing2789@gmail.com>,
lgirdwood@gmail.com, broonie@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, peron.clem@gmail.com
Cc: linux-sound@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ASoC: dt-bindings: sound: asahi-kasei,ak4118: Convert DT schema
Date: Sat, 30 May 2026 11:19:39 +0200 [thread overview]
Message-ID: <8219cc01-e13a-484d-a335-6e638671b9a6@kernel.org> (raw)
In-Reply-To: <20260524150231.109157-1-manishbaing2789@gmail.com>
On 24/05/2026 17:02, Manish Baing wrote:
> Convert the Asahi Kasei AK4118 S/PDIF transceiver bindings from
> text format to YAML schema.
>
> Signed-off-by: Manish Baing <manishbaing2789@gmail.com>
> ---
> Changes in v2:
> - Restored legacy 'irq-gpios' property to prevent C driver probe failure.
> - Added 'reset-gpios' and 'irq-gpios' to the required properties list.
>
> .../devicetree/bindings/sound/ak4118.txt | 22 -------
> .../bindings/sound/asahi-kasei,ak4118.yaml | 58 +++++++++++++++++++
> 2 files changed, 58 insertions(+), 22 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/sound/ak4118.txt
> create mode 100644 Documentation/devicetree/bindings/sound/asahi-kasei,ak4118.yaml
Organize your patches targeting one subsystem into one patchset. You
sent a lot and you make EXACTLY the same mistakes everywhere. So now I
need to replay to 10 different emails?
Well, you don't even give time to review, but immediately send v2.
Please slow down and put attention to this work.
I expect answers:
1. Did you analyze existing users of this binding?
2. If so, which users? How did you analyze them?
Best regards,
Krzysztof
prev parent reply other threads:[~2026-05-30 9:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-24 15:02 [PATCH v2] ASoC: dt-bindings: sound: asahi-kasei,ak4118: Convert DT schema Manish Baing
2026-05-30 9:19 ` Krzysztof Kozlowski [this message]
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=8219cc01-e13a-484d-a335-6e638671b9a6@kernel.org \
--to=krzk@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=manishbaing2789@gmail.com \
--cc=peron.clem@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox