linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Matti Vaittinen <mazziesaccount@gmail.com>,
	Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
Cc: Mark Brown <broonie@kernel.org>,
	Matteo Croce <mcroce@microsoft.com>,
	linux-kernel@vger.kernel.org, robh+dt@kernel.org,
	bjorn.andersson@linaro.org, Kees Cook <keescook@chromium.org>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	linux-arm-msm@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Andy Shevchenko <andy.shevchenko@gmail.com>,
	Guenter Roeck <linux@roeck-us.net>,
	Josef Bacik <josef@toxicpanda.com>,
	linux-pm@vger.kernel.org, Mike Rapoport <rppt@kernel.org>,
	Amit Kucheria <amitk@kernel.org>,
	devicetree@vger.kernel.org, Petr Mladek <pmladek@suse.com>,
	Zhang Rui <rui.zhang@intel.com>,
	Kai-Heng Feng <kai.heng.feng@canonical.com>,
	lgirdwood@gmail.com,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	linux-renesas-soc@vger.kernel.org, agross@kernel.org,
	linux-power <linux-power@fi.rohmeurope.com>
Subject: Re: [PATCH RESEND v10 00/11] Extend regulator notification support
Date: Mon, 21 Jun 2021 19:45:52 +0100	[thread overview]
Message-ID: <162430087046.9551.16763333166755641433.b4-ty@kernel.org> (raw)
In-Reply-To: <cover.1622628333.git.matti.vaittinen@fi.rohmeurope.com>

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

      parent reply	other threads:[~2021-06-21 18:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-03  5:40 [PATCH RESEND v10 00/11] Extend regulator notification support Matti Vaittinen
2021-06-03  5:40 ` [PATCH RESEND v10 01/11] dt_bindings: Add protection limit properties Matti Vaittinen
2021-06-03  5:40 ` [PATCH RESEND v10 02/11] reboot: Add hardware protection power-off Matti Vaittinen
2021-06-18  8:25   ` Daniel Lezcano
2021-06-03  5:41 ` [PATCH RESEND v10 03/11] thermal: Use generic HW-protection shutdown API Matti Vaittinen
2021-06-17 16:18   ` Daniel Lezcano
2021-06-03  5:41 ` [PATCH RESEND v10 04/11] regulator: add warning flags Matti Vaittinen
2021-06-03  5:41 ` [PATCH RESEND v10 05/11] regulator: move rdev_print helpers to internal.h Matti Vaittinen
2021-06-03  5:41 ` [PATCH RESEND v10 06/11] regulator: IRQ based event/error notification helpers Matti Vaittinen
2021-06-03  5:42 ` [PATCH RESEND v10 07/11] regulator: add property parsing and callbacks to set protection limits Matti Vaittinen
2021-06-03  5:42 ` [PATCH RESEND v10 08/11] dt-bindings: regulator: bd9576 add FET ON-resistance for OCW Matti Vaittinen
2021-06-03  5:42 ` [PATCH RESEND v10 09/11] regulator: bd9576: Support error reporting Matti Vaittinen
2021-06-03  5:43 ` [PATCH RESEND v10 10/11] regulator: bd9576: Fix the driver name in id table Matti Vaittinen
2021-06-03  5:43 ` [PATCH RESEND v10 11/11] MAINTAINERS: Add reviewer for regulator irq_helpers Matti Vaittinen
2021-06-17 12:37 ` [PATCH RESEND v10 00/11] Extend regulator notification support Mark Brown
2021-06-21 18:45 ` Mark Brown [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=162430087046.9551.16763333166755641433.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=agross@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=amitk@kernel.org \
    --cc=andy.shevchenko@gmail.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=josef@toxicpanda.com \
    --cc=kai.heng.feng@canonical.com \
    --cc=keescook@chromium.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-power@fi.rohmeurope.com \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=matti.vaittinen@fi.rohmeurope.com \
    --cc=mazziesaccount@gmail.com \
    --cc=mcroce@microsoft.com \
    --cc=pmladek@suse.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=robh+dt@kernel.org \
    --cc=rppt@kernel.org \
    --cc=rui.zhang@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).