From: "Rob Herring (Arm)" <robh@kernel.org>
To: Jihed Chaibi <jihed.chaibi.dev@gmail.com>
Cc: linux-kernel@vger.kernel.org, conor+dt@kernel.org,
patches@opensource.cirrus.com, matteomartelli3@gmail.com,
broonie@kernel.org, shuah@kernel.org, zhoubinbin@loongson.cn,
krzk+dt@kernel.org, devicetree@vger.kernel.org,
KCHSU0@nuvoton.com, linux-sound@vger.kernel.org,
katsuhiro@katsuster.net, lgirdwood@gmail.com, drake@endlessm.com
Subject: Re: [PATCH v2 3/3] ASoC: dt-bindings: wlf,wm8960: Document routing strings (pin names)
Date: Wed, 3 Sep 2025 18:55:40 -0500 [thread overview]
Message-ID: <175694373992.3390745.12577037587339202310.robh@kernel.org> (raw)
In-Reply-To: <20250903160119.83625-4-jihed.chaibi.dev@gmail.com>
On Wed, 03 Sep 2025 18:01:19 +0200, Jihed Chaibi wrote:
> Add a list of the wm8960 pin names to the binding's description to make
> it self-contained and improve the user experience for board developers.
>
> Signed-off-by: Jihed Chaibi <jihed.chaibi.dev@gmail.com>
>
> ---
> Changes in v2:
> - No changes, this file is already refering to device pins.
> ---
> .../devicetree/bindings/sound/wlf,wm8960.yaml | 22 +++++++++++++++++++
> 1 file changed, 22 insertions(+)
>
Acked-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2025-09-03 23:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 16:01 [PATCH v2 0/3] ASoC: dt-bindings: Document routing strings for various codecs Jihed Chaibi
2025-09-03 16:01 ` [PATCH v2 1/3] ASoC: dt-bindings: everest,es8316: Document routing strings Jihed Chaibi
2025-09-03 23:55 ` Rob Herring (Arm)
2025-09-04 11:47 ` Binbin Zhou
2025-09-03 16:01 ` [PATCH v2 2/3] ASoC: dt-bindings: nuvoton,nau8825: " Jihed Chaibi
2025-09-03 23:55 ` Rob Herring (Arm)
2025-09-03 16:01 ` [PATCH v2 3/3] ASoC: dt-bindings: wlf,wm8960: Document routing strings (pin names) Jihed Chaibi
2025-09-03 23:55 ` Rob Herring (Arm) [this message]
2025-09-04 8:42 ` Charles Keepax
2025-09-04 18:09 ` [PATCH v2 0/3] ASoC: dt-bindings: Document routing strings for various codecs Mark Brown
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=175694373992.3390745.12577037587339202310.robh@kernel.org \
--to=robh@kernel.org \
--cc=KCHSU0@nuvoton.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=drake@endlessm.com \
--cc=jihed.chaibi.dev@gmail.com \
--cc=katsuhiro@katsuster.net \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=matteomartelli3@gmail.com \
--cc=patches@opensource.cirrus.com \
--cc=shuah@kernel.org \
--cc=zhoubinbin@loongson.cn \
/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