[v1,0/6] ASoC: Fix gpiolib dependencies

Message

Mark Brown Feb. 2, 2022, 7:23 p.m. UTC

This series removes a bunch of spurious selects of gpiolib that were
causing noise in randconfig build tests.

Mark Brown (6):
  ASoC: dmic: Remove spurious gpiolib select
  ASoC: rt9120: Remove spurious gpiolib select
  ASoC: simple-amplifier: Remove spurious gpiolib select
  ASoC: max9759: Remove spurious gpiolib select
  ASoC: zl38060: Remove spurious gpiolib select
  ASoC: simple-mux: Depend on gpiolib rather than selecting it

 sound/soc/codecs/Kconfig | 8 ++------
 1 file changed, 2 insertions(+), 6 deletions(-)


base-commit: e783362eb54cd99b2cac8b3a9aeac942e6f6ac07

Comments

Mark Brown Feb. 8, 2022, 6:59 p.m. UTC | #1

On Wed, 2 Feb 2022 19:23:27 +0000, Mark Brown wrote:
> This series removes a bunch of spurious selects of gpiolib that were
> causing noise in randconfig build tests.
> 
> Mark Brown (6):
>   ASoC: dmic: Remove spurious gpiolib select
>   ASoC: rt9120: Remove spurious gpiolib select
>   ASoC: simple-amplifier: Remove spurious gpiolib select
>   ASoC: max9759: Remove spurious gpiolib select
>   ASoC: zl38060: Remove spurious gpiolib select
>   ASoC: simple-mux: Depend on gpiolib rather than selecting it
> 
> [...]

Applied to

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

Thanks!

[1/6] ASoC: dmic: Remove spurious gpiolib select
      commit: 823868f59ff4f1a8889120bc71a216542b79d909
[2/6] ASoC: rt9120: Remove spurious gpiolib select
      commit: 2cc12ef489a39d22230d4029c9890d27902a855b
[3/6] ASoC: simple-amplifier: Remove spurious gpiolib select
      commit: 44bd27c42a1c9a00f1fbcb58301a7f3e6f5cdd0f
[4/6] ASoC: max9759: Remove spurious gpiolib select
      commit: c29744876071c3186871515b3f849a884dc47241
[5/6] ASoC: zl38060: Remove spurious gpiolib select
      commit: 8e70aaae32b72d3088d18a3447b67112b3f5979a
[6/6] ASoC: simple-mux: Depend on gpiolib rather than selecting it
      commit: 805fff750107bce59f769a54f77205a8c4c37705

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