linux-kernel - Re: [PATCH] ASoC: amd: yc: Add quirk for ASUS Vivobook S15 M3502RA

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: <172864480352.3868579.17081032898194754716.b4-ty@kernel.org>
Date: Fri, 11 Oct 2024 12:06:43 +0100
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, Christian Heusel <christian@...sel.eu>
Cc: Thorsten Leemhuis <linux@...mhuis.info>, linux-sound@...r.kernel.org, 
 linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org
Subject: Re: [PATCH] ASoC: amd: yc: Add quirk for ASUS Vivobook S15 M3502RA

On Thu, 10 Oct 2024 15:32:11 +0200, Christian Heusel wrote:
> As reported the builtin microphone doesn't work on the ASUS Vivobook
> model S15 OLED M3502RA. Therefore add a quirk for it to make it work.
> 
> 

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 ASUS Vivobook S15 M3502RA
      commit: 182fff3a2aafe4e7f3717a0be9df2fe2ed1a77de

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