From: Tzung-Bi Shih <tzungbi@kernel.org>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Fabio Estevam <festevam@denx.de>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Zhang Rui <rui.zhang@intel.com>,
Lukasz Luba <lukasz.luba@arm.com>,
Jonathan Corbet <corbet@lwn.net>, Serge Hallyn <serge@hallyn.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Matti Vaittinen <mazziesaccount@gmail.com>,
Benson Leung <bleung@chromium.org>,
Guenter Roeck <groeck@chromium.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
linux-doc@vger.kernel.org, linux-security-module@vger.kernel.org,
chrome-platform@lists.linux.dev, devicetree@vger.kernel.org,
kernel@pengutronix.de
Subject: Re: [PATCH v2 06/12] reboot: indicate whether it is a HARDWARE PROTECTION reboot or shutdown
Date: Mon, 20 Jan 2025 07:11:48 +0000 [thread overview]
Message-ID: <Z433ND-LvkGo2se2@google.com> (raw)
In-Reply-To: <20250113-hw_protection-reboot-v2-6-161d3fc734f0@pengutronix.de>
On Mon, Jan 13, 2025 at 05:25:31PM +0100, Ahmad Fatoum wrote:
> It currently depends on the caller, whether we attempt a hardware
> protection shutdown (poweroff) or a reboot. A follow-up commit will make
> this partially user-configurable, so it's a good idea to have the
> emergency message clearly state whether the kernel is going for a reboot
> or a shutdown.
>
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
Reviewed-by: Tzung-Bi Shih <tzungbi@kernel.org>
next prev parent reply other threads:[~2025-01-20 7:11 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 16:25 [PATCH v2 00/12] reboot: support runtime configuration of emergency hw_protection action Ahmad Fatoum
2025-01-13 16:25 ` [PATCH v2 01/12] reboot: replace __hw_protection_shutdown bool action parameter with an enum Ahmad Fatoum
2025-01-20 7:10 ` Tzung-Bi Shih
2025-01-21 9:27 ` Ahmad Fatoum
2025-01-13 16:25 ` [PATCH v2 02/12] reboot: reboot, not shutdown, on hw_protection_reboot timeout Ahmad Fatoum
2025-01-20 7:10 ` Tzung-Bi Shih
2025-01-22 11:28 ` Matti Vaittinen
2025-02-17 20:22 ` Ahmad Fatoum
2025-02-18 6:45 ` Matti Vaittinen
2025-01-13 16:25 ` [PATCH v2 03/12] docs: thermal: sync hardware protection doc with code Ahmad Fatoum
2025-01-20 7:11 ` Tzung-Bi Shih
2025-01-21 9:29 ` Ahmad Fatoum
2025-01-22 11:01 ` Matti Vaittinen
2025-01-13 16:25 ` [PATCH v2 04/12] reboot: describe do_kernel_restart's cmd argument in kernel-doc Ahmad Fatoum
2025-01-20 7:11 ` Tzung-Bi Shih
2025-01-13 16:25 ` [PATCH v2 05/12] reboot: rename now misleading __hw_protection_shutdown symbols Ahmad Fatoum
2025-01-20 7:11 ` Tzung-Bi Shih
2025-01-13 16:25 ` [PATCH v2 06/12] reboot: indicate whether it is a HARDWARE PROTECTION reboot or shutdown Ahmad Fatoum
2025-01-20 7:11 ` Tzung-Bi Shih [this message]
2025-01-13 16:25 ` [PATCH v2 07/12] reboot: add support for configuring emergency hardware protection action Ahmad Fatoum
2025-01-20 7:12 ` Tzung-Bi Shih
2025-01-21 9:35 ` Ahmad Fatoum
2025-01-13 16:25 ` [PATCH v2 08/12] regulator: allow user configuration of " Ahmad Fatoum
2025-01-20 7:12 ` Tzung-Bi Shih
2025-01-22 11:18 ` Matti Vaittinen
2025-01-13 16:25 ` [PATCH v2 09/12] platform/chrome: cros_ec_lpc: prepare for hw_protection_shutdown removal Ahmad Fatoum
2025-01-20 7:12 ` Tzung-Bi Shih
2025-01-13 16:25 ` [PATCH v2 10/12] dt-bindings: thermal: give OS some leeway in absence of critical-action Ahmad Fatoum
2025-01-13 16:25 ` [PATCH v2 11/12] thermal: core: allow user configuration of hardware protection action Ahmad Fatoum
2025-01-20 7:12 ` Tzung-Bi Shih
2025-01-13 16:25 ` [PATCH v2 12/12] reboot: retire hw_protection_reboot and hw_protection_shutdown helpers Ahmad Fatoum
2025-01-20 7:13 ` Tzung-Bi Shih
2025-01-14 0:33 ` [PATCH v2 00/12] reboot: support runtime configuration of emergency hw_protection action Andrew Morton
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=Z433ND-LvkGo2se2@google.com \
--to=tzungbi@kernel.org \
--cc=a.fatoum@pengutronix.de \
--cc=akpm@linux-foundation.org \
--cc=bleung@chromium.org \
--cc=broonie@kernel.org \
--cc=chrome-platform@lists.linux.dev \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@denx.de \
--cc=groeck@chromium.org \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=mazziesaccount@gmail.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=rui.zhang@intel.com \
--cc=serge@hallyn.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.