linux-kernel - Re: [PATCH] ASoC: amd: yc: Add quirk for HP 200 G2a 16

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: <177012032894.85387.17295204152918099803.b4-ty@kernel.org>
Date: Tue, 03 Feb 2026 12:05:28 +0000
From: Mark Brown <broonie@...nel.org>
To: Dirk Su <dirk.su@...onical.com>
Cc: Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, Lane Odenbach <laodenbach@...il.com>, 
 Oliver Schramm <oliver.schramm97@...il.com>, Adam Queler <queler@...il.com>, 
 Mario Limonciello <mario.limonciello@....com>, 
 Gabriel Santese <santesegabriel@...il.com>, 
 Raven Black <ravenblack@...il.com>, Radhi Bajahaw <bajahawradhi@...il.com>, 
 Alexandru Andries <alex.andries.aa@...il.com>, 
 Talhah Peerbhai <talhah.peerbhai@...il.com>, 
 meowmeowbeanz <meowmeowbeanz@....com>, Yuzuru10 <yuzuru_10@...ton.me>, 
 keenplify <keenplify@...il.com>, Syed Saba kareem <syed.sabakareem@....com>, 
 linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: amd: yc: Add quirk for HP 200 G2a 16

On Thu, 29 Jan 2026 14:50:19 +0800, Dirk Su wrote:
> Fix the missing mic on HP 200 G2a 16 by adding quirk with the
> board ID 8EE4
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: amd: yc: Add quirk for HP 200 G2a 16
      commit: 611c7d2262d5645118e0b3a9a88475d35a8366f2

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