linux-kernel - Re: [PATCH] ASoC: fix unmet dependency on GPIOLIB

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: <163498938018.2020965.6267176645734620337.b4-ty@kernel.org>
Date:   Sat, 23 Oct 2021 12:43:07 +0100
From:   Mark Brown <broonie@...nel.org>
To:     linux-kernel@...r.kernel.org, Julian Braha <julianbraha@...il.com>,
        alsa-devel@...a-project.org
Cc:     Mark Brown <broonie@...nel.org>, ajitp@...eaurora.org,
        tiwai@...e.com, srinivas.kandagatla@...aro.org,
        bgoswami@...eaurora.org, lgirdwood@...il.com, perex@...ex.cz
Subject: Re: [PATCH] ASoC: fix unmet dependency on GPIOLIB

On Sun, 10 Oct 2021 17:56:27 -0400, Julian Braha wrote:
> When SND_SOC_SC7180 or SND_SOC_STORM is selected,
> and GPIOLIB is not selected, Kbuild gives the following
> warning:
> 
> WARNING: unmet direct dependencies detected for SND_SOC_MAX98357A
>   Depends on [n]: SOUND [=y] && !UML && SND [=y] && SND_SOC [=y] && GPIOLIB [=n]
>   Selected by [y]:
>   - SND_SOC_STORM [=y] && SOUND [=y] && !UML && SND [=y] && SND_SOC [=y] && SND_SOC_QCOM [=y]
>   - SND_SOC_SC7180 [=y] && SOUND [=y] && !UML && SND [=y] && SND_SOC [=y] && SND_SOC_QCOM [=y] && I2C [=y]
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: fix unmet dependency on GPIOLIB
      commit: 6cace797f1a8d54ecb42a3d327cbc0b231114ed0

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