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

[-- Attachment #1: Type: text/plain, Size: 534 bytes --]

On Thu, Jun 03, 2021 at 08:40:07AM +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/

Any thoughts on the reboot or thermal patches?  In the absence of any
further feedback by the end of the week I might go ahead and apply
things to the regulator tree if that's OK with people.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2021-06-17 12:38 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 ` Mark Brown [this message]
2021-06-21 18:45 ` [PATCH RESEND v10 00/11] Extend regulator notification support Mark Brown

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=20210617123738.GC5067@sirena.org.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.