public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Liam Girdwood <lgirdwood@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	 Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	 Conor Dooley <conor+dt@kernel.org>,
	 Oleksij Rempel <o.rempel@pengutronix.de>
Cc: kernel@pengutronix.de, linux-kernel@vger.kernel.org,
	 devicetree@vger.kernel.org
Subject: Re: [PATCH v4 0/5] regulator: add under-voltage support (part 2)
Date: Mon, 13 Nov 2023 19:40:20 +0000	[thread overview]
Message-ID: <169990442012.3294075.3943279581886493793.b4-ty@kernel.org> (raw)
In-Reply-To: <20231026144824.4065145-1-o.rempel@pengutronix.de>

On Thu, 26 Oct 2023 16:48:19 +0200, Oleksij Rempel wrote:
> This series add under-voltage and emergency shutdown for system critical
> regulators
> 
> changes v4:
> - rebase against latest regulator/for-next
> - drop mainlined patches
> - rename regulator-uv-survival-time-ms to regulator-uv-less-critical-window-ms
>   to fit it to actual use case
> - avoid some of words in commit messages
> - us switch case to parse critical events
> 
> [...]

Applied to

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

Thanks!

[1/5] regulator: dt-bindings: Add system-critical-regulator property
      commit: 0e1c8dcbdecefea93dee19419b2f67dca591dd42
[2/5] regulator: Introduce handling for system-critical under-voltage events
      commit: 8156c7dd47b92fc4a70c9ea58e7a9e88c8bc32be
[3/5] regulator: dt-bindings: Allow system-critical marking for fixed-regulator
      commit: 633cd1c0a9de7609f97c0c86e3ac81153e8263b0
[4/5] regulator: dt-bindings: Add 'regulator-uv-less-critical-window-ms' property
      commit: 759e2bd96971763db1cfaf6cafc07654b12aa21e
[5/5] regulator: Implement uv_survival_time for handling under-voltage events
      commit: 1e22152aa59d793743fc53051dd7a042f362aecb

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:[~2023-11-13 19:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-26 14:48 [PATCH v4 0/5] regulator: add under-voltage support (part 2) Oleksij Rempel
2023-10-26 14:48 ` [PATCH v4 1/5] regulator: dt-bindings: Add system-critical-regulator property Oleksij Rempel
2023-10-27 21:25   ` Rob Herring
2023-10-26 14:48 ` [PATCH v4 2/5] regulator: Introduce handling for system-critical under-voltage events Oleksij Rempel
2023-10-26 14:48 ` [PATCH v4 3/5] regulator: dt-bindings: Allow system-critical marking for fixed-regulator Oleksij Rempel
2023-10-27 21:24   ` Rob Herring
2023-10-27 21:32     ` Mark Brown
2023-10-30 15:45   ` Rob Herring
2023-10-26 14:48 ` [PATCH v4 4/5] regulator: dt-bindings: Add 'regulator-uv-less-critical-window-ms' property Oleksij Rempel
2023-10-27 21:26   ` Rob Herring
2023-10-26 14:48 ` [PATCH v4 5/5] regulator: Implement uv_survival_time for handling under-voltage events Oleksij Rempel
2023-11-13 19:40 ` 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=169990442012.3294075.3943279581886493793.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kernel@pengutronix.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=o.rempel@pengutronix.de \
    --cc=robh+dt@kernel.org \
    /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