From: Oder Chiou <oder_chiou@realtek.com>
To: "'Rob Herring'" <robh@kernel.org>
Cc: "cezary.rojewski@intel.com" <cezary.rojewski@intel.com>,
"broonie@kernel.org" <broonie@kernel.org>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"perex@perex.cz" <perex@perex.cz>,
"linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"Flove(HsinFu)" <flove@realtek.com>,
"Shuming [范書銘]" <shumingf@realtek.com>,
"Jack Yu" <jack.yu@realtek.com>,
"Derek [方德義]" <derek.fang@realtek.com>
Subject: RE: [PATCH v11 3/4] ASoC: dt-bindings: realtek,rt5575: add support for ALC5575
Date: Wed, 31 Dec 2025 02:26:46 +0000 [thread overview]
Message-ID: <2f37dcd86a9c41808b918371a23dfebb@realtek.com> (raw)
In-Reply-To: <20251230175333.GA854335-robh@kernel.org>
> -----Original Message-----
> From: Rob Herring <robh@kernel.org>
> Sent: Wednesday, December 31, 2025 1:54 AM
> To: Oder Chiou <oder_chiou@realtek.com>
> Cc: cezary.rojewski@intel.com; broonie@kernel.org; lgirdwood@gmail.com;
> krzk+dt@kernel.org; conor+dt@kernel.org; perex@perex.cz;
> linux-sound@vger.kernel.org; devicetree@vger.kernel.org;
> alsa-devel@alsa-project.org; Flove(HsinFu) <flove@realtek.com>; Shuming [范
> 書銘] <shumingf@realtek.com>; Jack Yu <jack.yu@realtek.com>; Derek [方德
> 義] <derek.fang@realtek.com>
> Subject: Re: [PATCH v11 3/4] ASoC: dt-bindings: realtek,rt5575: add support for
> ALC5575
>
>
> External mail : This email originated from outside the organization. Do not
> reply, click links, or open attachments unless you recognize the sender and
> know the content is safe.
>
>
>
> On Fri, Dec 26, 2025 at 04:39:14PM +0800, Oder Chiou wrote:
> > Audio codec with I2S, I2C and SPI.
> >
> > Signed-off-by: Oder Chiou <oder_chiou@realtek.com>
> > Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
> > ---
> > .../bindings/sound/realtek,rt5575.yaml | 61
> +++++++++++++++++++
> > 1 file changed, 61 insertions(+)
> > create mode 100644
> > Documentation/devicetree/bindings/sound/realtek,rt5575.yaml
>
> Where's the rest of the series? You are missing an In-Reply-To header and that
> breaks the tools (b4).
>
Hi Rob,
Sorry about that — this was a send-email threading issue.
I'll resend the full v11 series with proper In-Reply-To headers.
Thanks,
Oder
next prev parent reply other threads:[~2025-12-31 2:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-26 8:39 [PATCH v11 3/4] ASoC: dt-bindings: realtek,rt5575: add support for ALC5575 Oder Chiou
2025-12-30 17:53 ` Rob Herring
2025-12-31 2:26 ` Oder Chiou [this message]
2026-01-02 22:28 ` Rob Herring
-- strict thread matches above, loose matches on Subject: below --
2025-12-31 2:35 [PATCH v11 0/4] ASoC: rt5575: Add the codec driver for the ALC5575 Oder Chiou
2025-12-31 2:37 ` [PATCH v11 3/4] ASoC: dt-bindings: realtek,rt5575: add support for ALC5575 Oder Chiou
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=2f37dcd86a9c41808b918371a23dfebb@realtek.com \
--to=oder_chiou@realtek.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=conor+dt@kernel.org \
--cc=derek.fang@realtek.com \
--cc=devicetree@vger.kernel.org \
--cc=flove@realtek.com \
--cc=jack.yu@realtek.com \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=robh@kernel.org \
--cc=shumingf@realtek.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;
as well as URLs for NNTP newsgroup(s).