From: Jon Hunter <jonathanh@nvidia.com>
To: Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: 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: Wed, 14 Jan 2026 11:27:12 +0000 [thread overview]
Message-ID: <0e68c5f4-f68d-4544-bc7a-40694829db75@nvidia.com> (raw)
In-Reply-To: <176832669841.1106728.13139168898095349975.b4-ty@kernel.org>
Hi Mark, Rob,
On 13/01/2026 17:51, Mark Brown wrote:
> 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 to
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
>
> Thanks!
>
> [1/3] ASoC: dt-bindings: realtek,rt5640: Document mclk
> commit: 66b47b9c069fa548db64bde6a32d3b33aa05f740
> [2/3] ASoC: dt-bindings: realtek,rt5640: Update jack-detect
> commit: 25b858474497b5f7e2198f6fc9381488d9bdb55d
> [3/3] ASoC: dt-bindings: realtek,rt5640: Document port node
> commit: b540b4e157c4b24d0501e5e50ffba598d066de42
I noticed on today's -next I am getting the following error when running
the dtbs_check ...
Documentation/devicetree/bindings/sound/realtek,rt5640.yaml: ignoring, error parsing file
It appears that Rob also has merged similar fixes to the above and now
we have two lots of fixes merged and duplicated properties ...
bc5a847a80d4 ASoC: dt-bindings: realtek,rt5640: Various fixes
f66e7da2a6b1 ASoC: dt-bindings: realtek,rt5640: Allow 7 for realtek,jack-detect-source
101b982654ac ASoC: dt-bindings: realtek,rt5640: Add missing properties/node
b540b4e157c4 ASoC: dt-bindings: realtek,rt5640: Document port node
25b858474497 ASoC: dt-bindings: realtek,rt5640: Update jack-detect
66b47b9c069f ASoC: dt-bindings: realtek,rt5640: Document mclk
So we need to drop one set of fixes from one of the trees.
Thanks
Jon
--
nvpublic
next prev parent reply other threads:[~2026-01-14 11:27 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 [this message]
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
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=0e68c5f4-f68d-4544-bc7a-40694829db75@nvidia.com \
--to=jonathanh@nvidia.com \
--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-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox