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: <172080546390.557655.15542741446735034080.b4-ty@kernel.org>
Date: Fri, 12 Jul 2024 18:31:03 +0100
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, Prasad Kumpatla <quic_pkumpatl@...cinc.com>, 
 Mohammad Rafi Shaik <quic_mohs@...cinc.com>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 quic_rohkumar@...cinc.com
Subject: Re: [PATCH v2 0/3] Fix the unbalanced pm_runtime_enable in
 wcd937x-sdw soundwire slave

On Thu, 04 Jul 2024 13:47:20 +0530, Mohammad Rafi Shaik wrote:
> This patch set change will fix the unbalanced pm_runtime_enable in wcd937x-sdw soundwire slave.
> 
> And removed the string compare with widget name in MIC BIAS settings, instead
> of string compare use the MIC BIAS id's as value.
> 
> Removed separate handling for vdd-buck regulator supply which is not
> required. The vdd-buck regulator supply enabled using bulk enable.
> 
> [...]

Applied to

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

Thanks!

[1/3] ASoC: codecs: wcd937x-sdw: Fix Unbalanced pm_runtime_enable
      commit: 0ffc5a40ad21996c1c4b1d8a636c9051ea41a76e
[2/3] ASoC: codecs: wcd937x: Remove the string compare in MIC BIAS widget settings
      commit: a5f727f423101efd60a27bccd7680df429cef38a
[3/3] ASoC: codecs: wcd937x: Remove separate handling for vdd-buck supply
      commit: 216d04139a6d0ecaea9432178225b29d367da886

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