linux-kernel - Re: [PATCH] ASoC: SOF: Kconfig: Make SND_SOC_SOF_HDA

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:   Wed, 20 Apr 2022 22:40:52 +0100
From:   Mark Brown <broonie@...nel.org>
To:     rf@...nsource.cirrus.com, ranjani.sridharan@...ux.intel.com,
        kai.vehmanen@...ux.intel.com, peter.ujfalusi@...ux.intel.com,
        lgirdwood@...il.com, pierre-louis.bossart@...ux.intel.com
Cc:     sound-open-firmware@...a-project.org, alsa-devel@...a-project.org,
        patches@...nsource.cirrus.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: SOF: Kconfig: Make SND_SOC_SOF_HDA_PROBES tristate

On Thu, 7 Apr 2022 16:38:13 +0100, Richard Fitzgerald wrote:
> SND_SOC_SOF_HDA_PROBES must be tristate because the code it builds
> depends on code that is tristate.
> 
> If SND_SOC_SOF_HDA_PROBES is bool it leads to the following build
> inconsistency:
> 
> SND_SOC_SOF_HDA_COMMON=m
>   which selects SND_SOC_SOF_HDA_PROBES
>     but since this is a bool SND_SOC_SOF_HDA_PROBES=y
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: SOF: Kconfig: Make SND_SOC_SOF_HDA_PROBES tristate
      commit: e18610eaa66a1849aaa00ca43d605fb1a6fed800

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