[PATCH 0/3] regmap: Fix REGMAP selections

Geert Uytterhoeven posted 3 patches 2 years, 7 months ago
drivers/base/regmap/Kconfig | 16 +++++++++++++++-
drivers/mfd/Kconfig         |  1 -
sound/soc/codecs/Kconfig    |  1 +
3 files changed, 16 insertions(+), 2 deletions(-)
[PATCH 0/3] regmap: Fix REGMAP selections
Posted by Geert Uytterhoeven 2 years, 7 months ago
	Hi all,

This patch series fixes several missing selects related to REGMAP.

The first patch fixes a serious thinko I made when making the regmap
KUnit test depend on REGMAP.

The last two patches fix missing selects I discovered when diving deeper
into the REGMAP_* => REGMAP logic.

Thanks for your comments!

Geert Uytterhoeven (3):
  regmap: Replace "default y if" by select
  regmap: REGMAP_SLIMBUS should select REGMAP
  ASoC: codecs: SND_SOC_WCD934X should select REGMAP_IRQ

 drivers/base/regmap/Kconfig | 16 +++++++++++++++-
 drivers/mfd/Kconfig         |  1 -
 sound/soc/codecs/Kconfig    |  1 +
 3 files changed, 16 insertions(+), 2 deletions(-)

-- 
2.34.1

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds
Re: (subset) [PATCH 0/3] regmap: Fix REGMAP selections
Posted by Mark Brown 2 years, 7 months ago
On Thu, 06 Jul 2023 13:42:01 +0200, Geert Uytterhoeven wrote:
> 	Hi all,
> 
> This patch series fixes several missing selects related to REGMAP.
> 
> The first patch fixes a serious thinko I made when making the regmap
> KUnit test depend on REGMAP.
> 
> [...]

Applied to

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

Thanks!

[3/3] ASoC: codecs: SND_SOC_WCD934X should select REGMAP_IRQ
      commit: e231cd833f6463e9a1d54acae9614b513c74d45e

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