linux-kernel - Re: [PATCH v2 0/2] ASoC: Add Richtek RTQ9124 support

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: <174950285438.277844.8562649220481873561.b4-ty@kernel.org>
Date: Mon, 09 Jun 2025 22:00:54 +0100
From: Mark Brown <broonie@...nel.org>
To: Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, 
 cy_huang@...htek.com
Cc: Liam Girdwood <lgirdwood@...il.com>, Conor Dooley <conor+dt@...nel.org>, 
 Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>, 
 Roy Chiu <roy_chiu@...htek.com>, linux-sound@...r.kernel.org, 
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/2] ASoC: Add Richtek RTQ9124 support

On Mon, 09 Jun 2025 15:47:26 +0800, cy_huang@...htek.com wrote:
> This patch series adds Richtek RTQ9124 1x30W audio amplifier support.
> 
> v2:
> - Instead to add a dedicated rtq9124 document file, append the
>   description to the existed rt9123 yaml
> 
> ChiYuan Huang (2):
>   ASoC: dt-bindings: rt9123: Append RTQ9124 description
>   ASoC: codecs: Add support for Richtek RTQ9124
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: dt-bindings: rt9123: Append RTQ9124 description
      commit: 5c694e3a83d089df6b00747cf4627735ea14014e
[2/2] ASoC: codecs: Add support for Richtek RTQ9124
      commit: 1f5cdb6ab45e1c06ae0953609acbb52f8946b3e8

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