linux-kernel - Re: [PATCH] ASoC: amd: acp: Fix support for a Huawei Matebook laptop

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]

Date: Mon, 29 Jan 2024 23:08:45 +0000
From: Mark Brown <broonie@...nel.org>
To: alsa-devel@...a-project.org, Marian Postevca <posteuca@...ex.one>
Cc: linux-kernel@...r.kernel.org, linux-sound@...r.kernel.org, 
 Liam Girdwood <lgirdwood@...il.com>, Takashi Iwai <tiwai@...e.com>, 
 Jaroslav Kysela <perex@...ex.cz>
Subject: Re: [PATCH] ASoC: amd: acp: Fix support for a Huawei Matebook
 laptop

On Sun, 28 Jan 2024 19:22:29 +0200, Marian Postevca wrote:
> Previous commit that added support for Huawei MateBook D16 2021
> with Ryzen 4600H (HVY-WXX9 M1010) was incomplete.
> 
> To activate support for this laptop, the DMI table in
> acp3x-es83xx machine driver must also be updated.
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: amd: acp: Fix support for a Huawei Matebook laptop
      commit: 5513c5d0fb3d509cdd0a11afc18441c57eb7c94c

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