linux-kernel - Re: [PATCH v2 0/3] ASoC: dt-bindings: Document routing strings for various codecs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <175700938092.120028.16133127000007382726.b4-ty@kernel.org>
Date: Thu, 04 Sep 2025 19:09:40 +0100
From: Mark Brown <broonie@...nel.org>
To: linux-sound@...r.kernel.org, krzk+dt@...nel.org, 
 Jihed Chaibi <jihed.chaibi.dev@...il.com>
Cc: lgirdwood@...il.com, robh@...nel.org, conor+dt@...nel.org, 
 drake@...lessm.com, katsuhiro@...suster.net, matteomartelli3@...il.com, 
 zhoubinbin@...ngson.cn, KCHSU0@...oton.com, patches@...nsource.cirrus.com, 
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, shuah@...nel.org
Subject: Re: [PATCH v2 0/3] ASoC: dt-bindings: Document routing strings for
 various codecs

On Wed, 03 Sep 2025 18:01:16 +0200, Jihed Chaibi wrote:
> The series adds pin names for the es8316, wm8960, and nau8825
> codecs to their respective binding files to improve the user
> experience for board developers.
> 
> This v2 series addresses maintainer's feedback to rephrase the
> description to refer to the device's pins and ports rather than the
> driver.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/3] ASoC: dt-bindings: everest,es8316: Document routing strings
      commit: acd2fa47aac568052bd8321586be64958e3e93b2
[2/3] ASoC: dt-bindings: nuvoton,nau8825: Document routing strings
      commit: 118ddab8bb4a06fd5e13446d11d69e301044087d
[3/3] ASoC: dt-bindings: wlf,wm8960: Document routing strings (pin names)
      commit: 0ccc1eeda155c947d88ef053e0b54e434e218ee2

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark