linux-kernel - Re: [PATCH] regulator: userspace-consumer: add module device table

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: <170897708467.124661.5920836739900608106.b4-ty@kernel.org>
Date: Mon, 26 Feb 2024 19:51:24 +0000
From: Mark Brown <broonie@...nel.org>
To: linux-kernel@...r.kernel.org, John Keeping <jkeeping@...usicbrands.com>
Cc: Liam Girdwood <lgirdwood@...il.com>, Zev Weiss <zev@...ilderbeest.net>
Subject: Re: [PATCH] regulator: userspace-consumer: add module device table

On Mon, 26 Feb 2024 16:05:53 +0000, John Keeping wrote:
> The userspace consumer can be built as a module but it cannot be
> automatically probed as there is no device table to match it up with
> device tree nodes.
> 
> Add the missing macro so that the module can load automatically.
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: userspace-consumer: add module device table
      commit: 531a0c0cdbff9cecf41073220a826f8b1132f9ab

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