linux-kernel - Re: [PATCH] regmap: Provide user selectable option to enable 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: <168927917396.271035.8696798387681365367.b4-ty@kernel.org>
Date:   Thu, 13 Jul 2023 21:12:53 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Brendan Higgins <brendan.higgins@...ux.dev>,
        David Gow <davidgow@...gle.com>,
        Mark Brown <broonie@...nel.org>
Cc:     linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org,
        kunit-dev@...glegroups.com
Subject: Re: [PATCH] regmap: Provide user selectable option to enable
 regmap

On Wed, 12 Jul 2023 00:21:52 +0100, Mark Brown wrote:
> Since apparently enabling all the KUnit tests shouldn't enable any new
> subsystems it is hard to enable the regmap KUnit tests in normal KUnit
> testing scenarios that don't enable any drivers.  Add a Kconfig option
> to help with this and include it in the KUnit all tests config.
> 
> 

Applied to

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

Thanks!

[1/1] regmap: Provide user selectable option to enable regmap
      commit: 47ee108a113c72ec8ceee2c7af52c19ed72e6ad7

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