linux-kernel - Re: [PATCH RESEND v10 00/11] 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:52 +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>,
        Matteo Croce <mcroce@...rosoft.com>,
        linux-kernel@...r.kernel.org, robh+dt@...nel.org,
        bjorn.andersson@...aro.org, Kees Cook <keescook@...omium.org>,
        Daniel Lezcano <daniel.lezcano@...aro.org>,
        linux-arm-msm@...r.kernel.org,
        Andrew Morton <akpm@...ux-foundation.org>,
        Andy Shevchenko <andy.shevchenko@...il.com>,
        Guenter Roeck <linux@...ck-us.net>,
        Josef Bacik <josef@...icpanda.com>, linux-pm@...r.kernel.org,
        Mike Rapoport <rppt@...nel.org>,
        Amit Kucheria <amitk@...nel.org>, devicetree@...r.kernel.org,
        Petr Mladek <pmladek@...e.com>,
        Zhang Rui <rui.zhang@...el.com>,
        Kai-Heng Feng <kai.heng.feng@...onical.com>,
        lgirdwood@...il.com,
        "Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
        linux-renesas-soc@...r.kernel.org, agross@...nel.org,
        linux-power <linux-power@...rohmeurope.com>
Subject: Re: [PATCH RESEND v10 00/11] Extend regulator notification support

On Thu, 3 Jun 2021 08:40:07 +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/
> 
> In a nutshell - the series adds:
> 
> [...]

Applied to

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

Thanks!

[01/11] dt_bindings: Add protection limit properties
        commit: 673e851b7da81256e73fb738c550ec39bac1c9ff
[02/11] reboot: Add hardware protection power-off
        commit: dfa19b11385d4cf8f0242fd93e2073e25183c331
[03/11] thermal: Use generic HW-protection shutdown API
        commit: db0aeb4f074f7023da26fb65078197c39590346b
[04/11] regulator: add warning flags
        commit: e6c3092d43faf0aa095160cc552f8c05490d0962
[05/11] regulator: move rdev_print helpers to internal.h
        commit: 157d2230193ae683fcffcc1cd0a2c3aa4479955f
[06/11] regulator: IRQ based event/error notification helpers
        commit: 7111c6d1b31b42c8c758f6681e895a5116e3bad6
[07/11] regulator: add property parsing and callbacks to set protection limits
        commit: 89a6a5e56c8248a077d12424a1383a6b18ea840b
[08/11] dt-bindings: regulator: bd9576 add FET ON-resistance for OCW
        commit: 627793e4ca4f511837de893545baf0e1b8174dc2
[09/11] regulator: bd9576: Support error reporting
        commit: e7bf1fa58c46db9f72220c4472272d6da0a54c91
[10/11] regulator: bd9576: Fix the driver name in id table
        commit: e71e7d3df7eb712fc29b609bd712a63d60b81b5f
[11/11] MAINTAINERS: Add reviewer for regulator irq_helpers
        commit: d55444adedaee5a3024c61637032057fcf38491b

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