linux-kernel - Re: [PATCH] ASoC: amd: yc: Add quirk for Lenovo Yoga Pro 7 14ASP9

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: <174741893817.384649.2381968008958380317.b4-ty@kernel.org>
Date: Fri, 16 May 2025 19:08:58 +0100
From: Mark Brown <broonie@...nel.org>
To: lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com, 
 mario.limonciello@....com, linux-sound@...r.kernel.org, 
 linux-kernel@...r.kernel.org, Talhah Peerbhai <talhah.peerbhai@...il.com>
Subject: Re: [PATCH] ASoC: amd: yc: Add quirk for Lenovo Yoga Pro 7 14ASP9

On Fri, 16 May 2025 01:27:41 +0300, Talhah Peerbhai wrote:
> Similar to many other Lenovo models with AMD chips, the Lenovo
> Yoga Pro 7 14ASP9 (product name 83HN) requires a specific quirk
> to ensure internal mic detection. This patch adds a quirk fixing this.
> 
> 

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 Lenovo Yoga Pro 7 14ASP9
      commit: a28206060dc5848a1a2a15b7f6ac6223d869084d

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