linux-kernel - Re: [PATCH] ASoC: qcom: select correct WCD938X config for SC7280

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: <164668556615.3137316.2971642861768642189.b4-ty@kernel.org>
Date:   Mon, 07 Mar 2022 20:39:26 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Cc:     pierre-louis.bossart@...ux.intel.com, lgirdwood@...il.com,
        linux-kernel@...r.kernel.org, quic_srivasam@...cinc.com,
        tiwai@...e.com, alsa-devel@...a-project.org,
        Randy Dunlap <rdunlap@...radead.org>, perex@...ex.cz
Subject: Re: [PATCH] ASoC: qcom: select correct WCD938X config for SC7280

On Fri, 4 Mar 2022 16:09:34 +0000, Srinivas Kandagatla wrote:
> SC7280 config selected WCD938X instead of WCD938X_SDW Soundwire codecs.
> WCD938X_SDW actually selects WCD938X, so directly selecting WCD938X results
> in unmet dependencies and below warning
> 
> WARNING: unmet direct dependencies detected for SND_SOC_WCD938X
>   Depends on [n]: SOUND [=y] && !UML && SND [=y] && SND_SOC [=m]
>  && SND_SOC_WCD938X_SDW [=n] && (SOUNDWIRE [=n] || !SOUNDWIRE [=n])
>   Selected by [m]:
>   - SND_SOC_SC7280 [=m] && SOUND [=y] && !UML && SND [=y]
>  && SND_SOC [=m] && SND_SOC_QCOM [=m] && (I2C [=y] && SOUNDWIRE [=n] ||
>  COMPILE_TEST [=y])
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: qcom: select correct WCD938X config for SC7280
      commit: 6ed5dbba6c971fe644f5c2b4aae436b39da99f18

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