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: <177012032065.85387.285905871638457968.b4-ty@kernel.org>
Date: Tue, 03 Feb 2026 12:05:20 +0000
From: Mark Brown <broonie@...nel.org>
To: Tagir Garaev <tgaraev653@...il.com>
Cc: alsa-devel@...a-project.org, linux-kernel@...r.kernel.org, 
 Pierre-Louis Bossart <pierre-louis.bossart@...ux.dev>
Subject: Re: [RFC PATCH] ASoC: Intel: sof_es8336: Add DMI quirk for Huawei
 BOD-WXX9

On Sun, 01 Feb 2026 15:17:28 +0300, Tagir Garaev wrote:
> Add DMI entry for Huawei Matebook D (BOD-WXX9) with HEADPHONE_GPIO
> and DMIC quirks.
> 
> This device has ES8336 codec with:
> - GPIO 16 (headphone-enable) for headphone amplifier control
> - GPIO 17 (speakers-enable) for speaker amplifier control
> - GPIO 269 for jack detection IRQ
> - 2-channel DMIC
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: Intel: sof_es8336: Add DMI quirk for Huawei BOD-WXX9
      commit: 6b641122d31f9d33e7d60047ee0586d1659f3f54

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


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ