linux-kernel - Re: [PATCH v5 0/7] Extend regulator notification support

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, 21 Jun 2021 19:45:54 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Matti Vaittinen <mazziesaccount@...il.com>,
        Matti Vaittinen <matti.vaittinen@...rohmeurope.com>
Cc:     Mark Brown <broonie@...nel.org>, linux-kernel@...r.kernel.org,
        Rob Herring <robh+dt@...nel.org>,
        linux-arm-msm@...r.kernel.org, Andy Gross <agross@...nel.org>,
        linux-power@...rohmeurope.com, devicetree@...r.kernel.org,
        Liam Girdwood <lgirdwood@...il.com>,
        linux-renesas-soc@...r.kernel.org,
        Bjorn Andersson <bjorn.andersson@...aro.org>
Subject: Re: [PATCH v5 0/7] Extend regulator notification support

On Tue, 6 Apr 2021 14:18:04 +0300, Matti Vaittinen wrote:
> Extend regulator notification support
> 
> This series extends the regulator notification and error flag support. Initial
> discussion on the topic can be found here:
> https://lore.kernel.org/lkml/6046836e22b8252983f08d5621c35ececb97820d.camel@fi.rohmeurope.com/
> 
> This series is built on top of the BD9576MUF support patch series v9
> which is currently in MFD tree at immutable branch ib-mfd-watchdog-5.13
> https://lore.kernel.org/lkml/cover.1615219345.git.matti.vaittinen@fi.rohmeurope.com/
> (The series should apply without those patches but there is compile time
> dependency to definitions brought in at the last patch of the BD9576
> series. This should be Ok though as there is a Kconfig dependency in
> BD9576 regulator driver)
> 
> [...]

Applied to

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

Thanks!

[1/7] dt_bindings: Add protection limit properties
      commit: 673e851b7da81256e73fb738c550ec39bac1c9ff
[2/7] regulator: add warning flags
      commit: e6c3092d43faf0aa095160cc552f8c05490d0962
[3/7] regulator: IRQ based event/error notification helpers
      commit: 7111c6d1b31b42c8c758f6681e895a5116e3bad6
[4/7] regulator: add property parsing and callbacks to set protection limits
      commit: 89a6a5e56c8248a077d12424a1383a6b18ea840b
[5/7] dt-bindings: regulator: bd9576 add FET ON-resistance for OCW
      commit: 627793e4ca4f511837de893545baf0e1b8174dc2
[6/7] regulator: bd9576: Support error reporting
      commit: e7bf1fa58c46db9f72220c4472272d6da0a54c91
[7/7] regulator: bd9576: Fix the driver name in id table
      commit: e71e7d3df7eb712fc29b609bd712a63d60b81b5f

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