linux-kernel - Re: [PATCH] ASoC: qcom: cleanup and fix dependency of QCOM

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:   Fri, 25 Nov 2022 14:27:02 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Cc:     linux-kernel@...r.kernel.org, tiwai@...e.com,
        alsa-devel@...a-project.org, lgirdwood@...il.com, perex@...ex.cz,
        kernel test robot <lkp@...el.com>
Subject: Re: [PATCH] ASoC: qcom: cleanup and fix dependency of QCOM_COMMON

On Thu, 24 Nov 2022 14:03:51 +0000, Srinivas Kandagatla wrote:
> SND_SOC_QCOM_COMMON depends on SOUNDWIRE for some symbols but this
> is not explicitly specified using Kconfig depends. On the other hand
> SND_SOC_QCOM_COMMON is also directly selected by the sound card
> Kconfigs, this could result in various combinations and some symbols
> ending up in modules and soundcard that uses those symbols as in-build
> driver.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: qcom: cleanup and fix dependency of QCOM_COMMON
      commit: 8d89cf6ff229ff31cd4f73f5b3928564b81fc41e

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