linux-kernel - Re: [PATCH 0/2] regulator: Convert Linear Technologies driver to maple tree cache

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]

Date:   Mon, 19 Jun 2023 22:36:09 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Liam Girdwood <lgirdwood@...il.com>,
        Mark Brown <broonie@...nel.org>
Cc:     linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] regulator: Convert Linear Technologies driver to
 maple tree cache

On Sat, 10 Jun 2023 14:59:52 +0100, Mark Brown wrote:
> There are a couple of Linear Technologies devices which can only do
> single register reads and writes so don't benefit from using the rbtree
> register cache rather than the more modern maple tree cache, update them
> to use maple tree.
> 
> 

Applied to

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

Thanks!

[1/2] regulator: ltc3589: Use maple tree register cache
      commit: 29890a15865deaf7f446119bcb5617b0cc76be03
[2/2] regulator: ltc3676: Use maple tree register cache
      commit: ce44a03db73f7ce7cca152e07bd9cbfc3c10a0ba

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