linux-kernel - Re: [PATCH 0/7] regulator: Set PROBE_PREFER_ASYNCHRONOUS for everything in drivers/regulator

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: <167933890042.207143.7298283262381290865.b4-ty@kernel.org>
Date:   Mon, 20 Mar 2023 19:01:40 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Douglas Anderson <dianders@...omium.org>
Cc:     mka@...omium.org, Liam Girdwood <lgirdwood@...il.com>,
        Saravana Kannan <saravanak@...gle.com>,
        dmitry.torokhov@...il.com, linux-kernel@...r.kernel.org,
        swboyd@...omium.org, briannorris@...omium.org
Subject: Re: [PATCH 0/7] regulator: Set PROBE_PREFER_ASYNCHRONOUS for
 everything in drivers/regulator

On Thu, 16 Mar 2023 12:54:37 -0700, Douglas Anderson wrote:
> This series directly follows from the discussion when I tried to turn
> on PROBE_PREFER_ASYNCHRONOUS just for the fixed-regulator [1] and
> attempts to switch everything in drivers/regulator over to async
> probe.
> 
> Like the similar patch series I did for the MMC subsystem a few years
> ago [2], I've split this patch series into batches corresponding to
> drivers corresponding to actively maintained stable kernel trees with
> the idea to break the patch series up somewhat.
> 
> [...]

Applied to

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

Thanks!

[1/7] regulator: Set PROBE_PREFER_ASYNCHRONOUS for drivers that existed in 4.14
      commit: 259b93b21a9ffe5117af4dfb5505437e463c6a5a
[2/7] regulator: Set PROBE_PREFER_ASYNCHRONOUS for drivers between 4.14 and 4.19
      commit: ed6962cc3e05ca77f526590f62587678149d5e58
[3/7] regulator: Set PROBE_PREFER_ASYNCHRONOUS for drivers between 4.19 and 5.4
      commit: d3b81d97d55871cb11412caedded440f1fddc4e9
[4/7] regulator: Set PROBE_PREFER_ASYNCHRONOUS for drivers between 5.4 and 5.10
      commit: 67dc71c61b64be85ce33d3332ca5511f9b1faef7
[5/7] regulator: Set PROBE_PREFER_ASYNCHRONOUS for drivers between 5.10 and 5.15
      commit: 46600ab142f8c2ecc2a647175fd86d53bc285a9a
[6/7] regulator: Set PROBE_PREFER_ASYNCHRONOUS for drivers between 5.15 and 6.1
      commit: 41cff178e3d6df28acd8490519a656c509b4496f
[7/7] regulator: Set PROBE_PREFER_ASYNCHRONOUS for drivers that are newer than 6.1
      commit: bdce47bb19cbf7784d48e93677c868a69dbae439

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