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: <172382104064.70235.8442859739541696689.b4-ty@kernel.org>
Date: Fri, 16 Aug 2024 16:10:40 +0100
From: Mark Brown <broonie@...nel.org>
To: srinivas.kandagatla@...aro.org
Cc: perex@...ex.cz, tiwai@...e.com, alsa-devel@...a-project.org, 
 linux-arm-msm@...r.kernel.org, linux-sound@...r.kernel.org, 
 linux-kernel@...r.kernel.org, amit.pundir@...aro.org, 
 dmitry.baryshkov@...aro.org, devicetree@...r.kernel.org, robh@...nel.org, 
 krzk+dt@...nel.org, conor+dt@...nel.org
Subject: Re: [PATCH] ASoC: dt-bindings: qcom,lpass-wsa-macro: correct
 clocks on SM8250

On Thu, 15 Aug 2024 17:53:20 +0100, srinivas.kandagatla@...aro.org wrote:
> we seems to have ended up with duplicate clocks for frame-sync on sm8250,
> it has both va and fsgen which are exactly same things. Remove the redundant
> va clock and make it align with other SoCs.
> 
> Codec driver does not even handle va clock, so remove this from the
> bindings and examples to avoid any confusion.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: dt-bindings: qcom,lpass-wsa-macro: correct clocks on SM8250
      commit: d08ea4193a72c5e3090240872ff7ed60a70716e6

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