From: Rob Herring <robh@kernel.org>
To: cy_huang@richtek.com
Cc: Mark Brown <broonie@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Otto lin <otto_lin@richtek.com>,
Allen Lin <allen_lin@richtek.com>,
devicetree@vger.kernel.org, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/4] ASoC: dt-bindings: Add bindings for Richtek rt9123
Date: Fri, 11 Apr 2025 11:09:26 -0500 [thread overview]
Message-ID: <20250411160926.GA3320801-robh@kernel.org> (raw)
In-Reply-To: <4a0b67438f82e7d8ed9968cc90acf419fc9c22cf.1744245663.git.cy_huang@richtek.com>
On Thu, Apr 10, 2025 at 08:58:10AM +0800, cy_huang@richtek.com wrote:
> From: ChiYuan Huang <cy_huang@richtek.com>
>
> Document the ASoC Richtek rt9123.
>
> Signed-off-by: ChiYuan Huang <cy_huang@richtek.com>
> ---
> .../bindings/sound/richtek,rt9123.yaml | 56 +++++++++++++++++++
> 1 file changed, 56 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/sound/richtek,rt9123.yaml
If you re-spin, drop 'bindings for ' in the subject of both patches. No
need to say 'bindings' twice.
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2025-04-11 16:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 0:58 [PATCH v2 0/4] ASoC: Add Richtek rt9123 and rt9123p support cy_huang
2025-04-10 0:58 ` [PATCH v2 1/4] ASoC: dt-bindings: Add bindings for Richtek rt9123 cy_huang
2025-04-11 16:09 ` Rob Herring [this message]
2025-04-10 0:58 ` [PATCH v2 2/4] ASoC: codecs: Add support " cy_huang
2025-04-10 0:58 ` [PATCH v2 3/4] ASoC: dt-bindings: Add bindings for Richtek rt9123p cy_huang
2025-04-11 16:09 ` Rob Herring (Arm)
2025-04-10 0:58 ` [PATCH v2 4/4] ASoC: codecs: Add support " cy_huang
2025-04-14 13:56 ` [PATCH v2 0/4] ASoC: Add Richtek rt9123 and rt9123p support 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=20250411160926.GA3320801-robh@kernel.org \
--to=robh@kernel.org \
--cc=allen_lin@richtek.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cy_huang@richtek.com \
--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=otto_lin@richtek.com \
--cc=perex@perex.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.