All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Rob Herring <robh@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>,
	 Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	 Jon Hunter <jonathanh@nvidia.com>,
	linux-sound@vger.kernel.org, devicetree@vger.kernel.org,
	 linux-tegra@vger.kernel.org
Subject: Re: [PATCH 0/3] ASoC: dt-bindings: realtek,rt5640: Various fixes
Date: Thu, 22 Jan 2026 13:21:24 +0100	[thread overview]
Message-ID: <aXIWEP9lH1CyacnO@orome> (raw)
In-Reply-To: <CAL_Jsq+LUsfcU_-zPo88acsL_C6red=4jzmeca3ZCeyPgHDBvA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1389 bytes --]

On Tue, Jan 20, 2026 at 07:35:53PM -0600, Rob Herring wrote:
> On Fri, Jan 16, 2026 at 6:59 PM Thierry Reding <thierry.reding@gmail.com> wrote:
> >
> > From: Thierry Reding <treding@nvidia.com>
> >
> >
> > On Thu, 08 Jan 2026 14:31:55 +0000, Jon Hunter wrote:
> > > This series includes fixes for the realtek,rt5640 dt-binding to address
> > > a few warnings that are observed when running the CHECK_DTBS=y for some
> > > DTBs that use this codec.
> > >
> > > Jon Hunter (3):
> > >   ASoC: dt-bindings: realtek,rt5640: Document mclk
> > >   ASoC: dt-bindings: realtek,rt5640: Update jack-detect
> > >   ASoC: dt-bindings: realtek,rt5640: Document port node
> > >
> > > [...]
> >
> > Applied, thanks!
> >
> > [1/3] ASoC: dt-bindings: realtek,rt5640: Document mclk
> >       commit: 601a821631c55014b02371740c39748d0af916c1
> > [2/3] ASoC: dt-bindings: realtek,rt5640: Update jack-detect
> >       commit: 2efe28d11cc19b69b19b9bcdb6f498c1bf842fbc
> > [3/3] ASoC: dt-bindings: realtek,rt5640: Document port node
> >       commit: b2788f6320722d6059f849f35a77eb082608c627
> 
> Please drop these. linux-next is broken. Plus Mark already said he applied them.

Sorry, I missed that. Unfortunately neither patchwork nor b4 show this
information, and I must've scolled by Mark's reply (or forgotten about
it). Dropped from the Tegra tree now.

Thanks,
Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2026-01-22 12:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-08 14:31 [PATCH 0/3] ASoC: dt-bindings: realtek,rt5640: Various fixes Jon Hunter
2026-01-08 14:31 ` [PATCH 1/3] ASoC: dt-bindings: realtek,rt5640: Document mclk Jon Hunter
2026-01-09  8:50   ` Krzysztof Kozlowski
2026-01-08 14:31 ` [PATCH 2/3] ASoC: dt-bindings: realtek,rt5640: Update jack-detect Jon Hunter
2026-01-09  8:54   ` Krzysztof Kozlowski
2026-01-08 14:31 ` [PATCH 3/3] ASoC: dt-bindings: realtek,rt5640: Document port node Jon Hunter
2026-01-09  8:55   ` Krzysztof Kozlowski
2026-01-13 17:51 ` [PATCH 0/3] ASoC: dt-bindings: realtek,rt5640: Various fixes Mark Brown
2026-01-14 11:27   ` Jon Hunter
2026-01-14 12:03     ` Mark Brown
2026-01-14 22:06       ` Mark Brown
2026-01-17  0:58 ` Thierry Reding
2026-01-21  1:35   ` Rob Herring
2026-01-22 12:21     ` Thierry Reding [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=aXIWEP9lH1CyacnO@orome \
    --to=thierry.reding@gmail.com \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=krzk+dt@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-sound@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --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 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.