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: <174983355678.217351.11777150034827074781.b4-ty@kernel.org>
Date: Fri, 13 Jun 2025 17:52:36 +0100
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, Terry Cheong <htcheong@...omium.org>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 bailideng@...gle.com, judyhsiao@...gle.com, yuhsuan@...gle.com
Subject: Re: [PATCH] ASoC: hdmi-codec: use SND_JACK_AVOUT as jack status

On Fri, 13 Jun 2025 16:51:27 +0800, Terry Cheong wrote:
> Use SND_JACK_AVOUT as the mask to align with hdac_hdmi driver so that we
> can determine HDMI/DP devices from event type.
> 
> Most drivers that uses hdmi-codec driver will not be affected since they
> are creating jacks with SND_JACK_LINEOUT mask. They will still report
> SND_JACK_LINEOUT when the jack status is updated with
> snd_soc_jack_report.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: hdmi-codec: use SND_JACK_AVOUT as jack status
      commit: 5eb8a0d7733d4cd32a776acf1d1aa1c7c01c8a14

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