linux-kernel - Re: [PATCH] ASoC: codecs: wcd938x: make sdw dependency explicit in Kconfig

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: <162627737185.54838.13473688985790712154.b4-ty@kernel.org>
Date:   Wed, 14 Jul 2021 16:55:19 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Cc:     Mark Brown <broonie@...nel.org>, linux-kernel@...r.kernel.org,
        alsa-devel@...a-project.org, kernel test robot <lkp@...el.com>,
        lgirdwood@...il.com
Subject: Re: [PATCH] ASoC: codecs: wcd938x: make sdw dependency explicit in Kconfig

On Tue, 13 Jul 2021 15:04:17 +0100, Srinivas Kandagatla wrote:
> currenlty wcd938x has only soundwire interface and depends on
> symbols from wcd938x soundwire module, so make this dependency
> explicit in Kconfig
> 
> Without this one of the randconfig endup setting
> CONFIG_SND_SOC_WCD938X=y
> CONFIG_SND_SOC_WCD938X_SDW=m
> resulting in some undefined reference to wcd938x_sdw* symbols.

Applied to

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

Thanks!

[1/1] ASoC: codecs: wcd938x: make sdw dependency explicit in Kconfig
      commit: 9431f8df233f808baa5fcc62b520cc6503fdf022

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