linux-kernel - Re: [PATCH v2 0/3] ASoC: Update rtq9128 document and source file

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: <176831220432.70484.10730103796055155517.b4-ty@kernel.org>
Date: Tue, 13 Jan 2026 13:50:04 +0000
From: Mark Brown <broonie@...nel.org>
To: Krzysztof Kozlowski <krzk+dt@...nel.org>, cy_huang@...htek.com
Cc: Rob Herring <robh@...nel.org>, Conor Dooley <conor+dt@...nel.org>, 
 Liam Girdwood <lgirdwood@...il.com>, musk_wang@...htek.com, 
 roy_chiu@...htek.com, allen_lin@...htek.com, devicetree@...r.kernel.org, 
 linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/3] ASoC: Update rtq9128 document and source file

On Mon, 12 Jan 2026 09:27:31 +0800, cy_huang@...htek.com wrote:
> This patch series include two parts
> - Update initial setting for rtq9128 specific feature
> - Add rtq9154 backward compatible with rtq9128
> 
> v2
> - Fix commit message typo
> 
> [...]

Applied to

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

Thanks!

[1/3] ASoC: codecs: rtq9128: Modify the chip initial setting
      commit: daf86dcdbb40c4a0e4b8e579c6eecf148560711f
[2/3] dt-bindings: sound: rtq9128: Add rtq9154 backward compatible
      commit: b7d53fe53cb57db1ca5743d2ac2db28140c37647
[3/3] ASoC: codecs: rtq9128: Add compatible changes for rtq9154
      commit: 6be9ea62afedef0f976eb3dba4c117be0c1d3809

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