linux-kernel - Re: [PATCH v2] regmap: Enable REGMAP when REGMAP

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: <176856976035.65534.17705282773581631797.b4-ty@kernel.org>
Date: Fri, 16 Jan 2026 13:22:40 +0000
From: Mark Brown <broonie@...nel.org>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>, 
 "Rafael J . Wysocki" <rafael@...nel.org>, 
 Danilo Krummrich <dakr@...nel.org>, 
 Geert Uytterhoeven <geert+renesas@...der.be>
Cc: linux-kernel@...r.kernel.org, Geert Uytterhoeven <geert@...ux-m68k.org>
Subject: Re: [PATCH v2] regmap: Enable REGMAP when REGMAP_SLIMBUS is
 enabled

On Thu, 15 Jan 2026 17:24:02 +0100, Geert Uytterhoeven wrote:
> Invisible symbol REGMAP defaults to y when any of the REGMAP_* symbols
> is enabled, effectively auto-enabling it when needed.  However,
> REGMAP_SLIMBUS is missing from the list.
> 
> Currently this does not cause any issues, as all symbols selecting
> REGMAP_SLIMBUS also select REGMAP and/or REGMAP_IRQ.  Add REGMAP_SLIMBUS
> to the list for consistency, and to prevent any future issues.
> 
> [...]

Applied to

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

Thanks!

[1/1] regmap: Enable REGMAP when REGMAP_SLIMBUS is enabled
      commit: dccc66b0e92d48d9a1908a3ccb8142e0ee3381f5

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