* [PATCH RESEND v10 02/11] reboot: Add hardware protection power-off
2021-06-03 5:40 [PATCH RESEND v10 00/11] Extend regulator notification support Matti Vaittinen
@ 2021-06-03 5:40 ` 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
` (2 subsequent siblings)
3 siblings, 1 reply; 7+ messages in thread
From: Matti Vaittinen @ 2021-06-03 5:40 UTC (permalink / raw)
To: Matti Vaittinen, Matti Vaittinen
Cc: Mark Brown, Kees Cook, Andy Shevchenko, Zhang Rui, Guenter Roeck,
agross, devicetree, linux-power, linux-kernel, linux-renesas-soc,
linux-arm-msm, bjorn.andersson, lgirdwood, robh+dt,
Daniel Lezcano, Amit Kucheria, Matteo Croce, Andrew Morton,
Petr Mladek, Rafael J. Wysocki, Mike Rapoport, Josef Bacik,
Kai-Heng Feng, linux-pm
[-- Attachment #1: Type: text/plain, Size: 5533 bytes --]
There can be few cases when we need to shut-down the system in order to
protect the hardware. Currently this is done at least by the thermal core
when temperature raises over certain limit.
Some PMICs can also generate interrupts for example for over-current or
over-voltage, voltage drops, short-circuit, ... etc. On some systems
these are a sign of hardware failure and only thing to do is try to
protect the rest of the hardware by shutting down the system.
Add shut-down logic which can be used by all subsystems instead of
implementing the shutdown in each subsystem. The logic is stolen from
thermal_core with difference of using atomic_t instead of a mutex in
order to allow calls directly from IRQ context and changing the WARN()
to pr_emerg() as discussed here:
https://lore.kernel.org/lkml/YJuPwAZroVZ%2Fw633@alley/
and here:
https://lore.kernel.org/linux-iommu/20210331093104.383705-4-geert+renesas@glider.be/
Signed-off-by: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
---
Changelog:
v10: (changes suggested by Petr Mladek and Geert)
- replace WARN() by pr_emerg()
v8: (changes suggested by Daniel Lezcano)
- replace a protection implemented by a flag + spin_lock_irqsave() with
simple atomic_dec_and_test().
- Split thermal-core changes and adding the new API to separate patches
v7:
- New patch
---
include/linux/reboot.h | 1 +
kernel/reboot.c | 79 ++++++++++++++++++++++++++++++++++++++++++
2 files changed, 80 insertions(+)
diff --git a/include/linux/reboot.h b/include/linux/reboot.h
index 3734cd8f38a8..af907a3d68d1 100644
--- a/include/linux/reboot.h
+++ b/include/linux/reboot.h
@@ -79,6 +79,7 @@ extern char poweroff_cmd[POWEROFF_CMD_PATH_LEN];
extern void orderly_poweroff(bool force);
extern void orderly_reboot(void);
+void hw_protection_shutdown(const char *reason, int ms_until_forced);
/*
* Emergency restart, callable from an interrupt handler.
diff --git a/kernel/reboot.c b/kernel/reboot.c
index a6ad5eb2fa73..f7440c0c7e43 100644
--- a/kernel/reboot.c
+++ b/kernel/reboot.c
@@ -7,6 +7,7 @@
#define pr_fmt(fmt) "reboot: " fmt
+#include <linux/atomic.h>
#include <linux/ctype.h>
#include <linux/export.h>
#include <linux/kexec.h>
@@ -518,6 +519,84 @@ void orderly_reboot(void)
}
EXPORT_SYMBOL_GPL(orderly_reboot);
+/**
+ * hw_failure_emergency_poweroff_func - emergency poweroff work after a known delay
+ * @work: work_struct associated with the emergency poweroff function
+ *
+ * This function is called in very critical situations to force
+ * a kernel poweroff after a configurable timeout value.
+ */
+static void hw_failure_emergency_poweroff_func(struct work_struct *work)
+{
+ /*
+ * We have reached here after the emergency shutdown waiting period has
+ * expired. This means orderly_poweroff has not been able to shut off
+ * the system for some reason.
+ *
+ * Try to shut down the system immediately using kernel_power_off
+ * if populated
+ */
+ pr_emerg("Hardware protection timed-out. Trying forced poweroff\n");
+ kernel_power_off();
+
+ /*
+ * Worst of the worst case trigger emergency restart
+ */
+ pr_emerg("Hardware protection shutdown failed. Trying emergency restart\n");
+ emergency_restart();
+}
+
+static DECLARE_DELAYED_WORK(hw_failure_emergency_poweroff_work,
+ hw_failure_emergency_poweroff_func);
+
+/**
+ * hw_failure_emergency_poweroff - Trigger an emergency system poweroff
+ *
+ * This may be called from any critical situation to trigger a system shutdown
+ * after a given period of time. If time is negative this is not scheduled.
+ */
+static void hw_failure_emergency_poweroff(int poweroff_delay_ms)
+{
+ if (poweroff_delay_ms <= 0)
+ return;
+ schedule_delayed_work(&hw_failure_emergency_poweroff_work,
+ msecs_to_jiffies(poweroff_delay_ms));
+}
+
+/**
+ * hw_protection_shutdown - Trigger an emergency system poweroff
+ *
+ * @reason: Reason of emergency shutdown to be printed.
+ * @ms_until_forced: Time to wait for orderly shutdown before tiggering a
+ * forced shudown. Negative value disables the forced
+ * shutdown.
+ *
+ * Initiate an emergency system shutdown in order to protect hardware from
+ * further damage. Usage examples include a thermal protection or a voltage or
+ * current regulator failures.
+ * NOTE: The request is ignored if protection shutdown is already pending even
+ * if the previous request has given a large timeout for forced shutdown.
+ * Can be called from any context.
+ */
+void hw_protection_shutdown(const char *reason, int ms_until_forced)
+{
+ static atomic_t allow_proceed = ATOMIC_INIT(1);
+
+ pr_emerg("HARDWARE PROTECTION shutdown (%s)\n", reason);
+
+ /* Shutdown should be initiated only once. */
+ if (!atomic_dec_and_test(&allow_proceed))
+ return;
+
+ /*
+ * Queue a backup emergency shutdown in the event of
+ * orderly_poweroff failure
+ */
+ hw_failure_emergency_poweroff(ms_until_forced);
+ orderly_poweroff(true);
+}
+EXPORT_SYMBOL_GPL(hw_protection_shutdown);
+
static int __init reboot_setup(char *str)
{
for (;;) {
--
2.25.4
--
Matti Vaittinen, Linux device drivers
ROHM Semiconductors, Finland SWDC
Kiviharjunlenkki 1E
90220 OULU
FINLAND
~~~ "I don't think so," said Rene Descartes. Just then he vanished ~~~
Simon says - in Latin please.
~~~ "non cogito me" dixit Rene Descarte, deinde evanescavit ~~~
Thanks to Simon Glass for the translation =]
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply related [flat|nested] 7+ messages in thread
* Re: [PATCH RESEND v10 02/11] reboot: Add hardware protection power-off
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
0 siblings, 0 replies; 7+ messages in thread
From: Daniel Lezcano @ 2021-06-18 8:25 UTC (permalink / raw)
To: Matti Vaittinen, Matti Vaittinen
Cc: Mark Brown, Kees Cook, Andy Shevchenko, Zhang Rui, Guenter Roeck,
agross, devicetree, linux-power, linux-kernel, linux-renesas-soc,
linux-arm-msm, bjorn.andersson, lgirdwood, robh+dt,
Amit Kucheria, Matteo Croce, Andrew Morton, Petr Mladek,
Rafael J. Wysocki, Mike Rapoport, Josef Bacik, Kai-Heng Feng,
linux-pm
On 03/06/2021 07:40, Matti Vaittinen wrote:
> There can be few cases when we need to shut-down the system in order to
> protect the hardware. Currently this is done at least by the thermal core
> when temperature raises over certain limit.
>
> Some PMICs can also generate interrupts for example for over-current or
> over-voltage, voltage drops, short-circuit, ... etc. On some systems
> these are a sign of hardware failure and only thing to do is try to
> protect the rest of the hardware by shutting down the system.
>
> Add shut-down logic which can be used by all subsystems instead of
> implementing the shutdown in each subsystem. The logic is stolen from
> thermal_core with difference of using atomic_t instead of a mutex in
> order to allow calls directly from IRQ context and changing the WARN()
> to pr_emerg() as discussed here:
> https://lore.kernel.org/lkml/YJuPwAZroVZ%2Fw633@alley/
> and here:
> https://lore.kernel.org/linux-iommu/20210331093104.383705-4-geert+renesas@glider.be/
>
> Signed-off-by: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
Acked-by: Daniel Lezcano <daniel.lezcano@linaro.org>
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
^ permalink raw reply [flat|nested] 7+ messages in thread
* [PATCH RESEND v10 03/11] thermal: Use generic HW-protection shutdown API
2021-06-03 5:40 [PATCH RESEND v10 00/11] Extend regulator notification support Matti Vaittinen
2021-06-03 5:40 ` [PATCH RESEND v10 02/11] reboot: Add hardware protection power-off Matti Vaittinen
@ 2021-06-03 5:41 ` Matti Vaittinen
2021-06-17 16:18 ` Daniel Lezcano
2021-06-17 12:37 ` [PATCH RESEND v10 00/11] Extend regulator notification support Mark Brown
2021-06-21 18:45 ` Mark Brown
3 siblings, 1 reply; 7+ messages in thread
From: Matti Vaittinen @ 2021-06-03 5:41 UTC (permalink / raw)
To: Matti Vaittinen, Matti Vaittinen
Cc: Mark Brown, Kees Cook, Andy Shevchenko, Zhang Rui, Guenter Roeck,
agross, devicetree, linux-power, linux-kernel, linux-renesas-soc,
linux-arm-msm, bjorn.andersson, lgirdwood, robh+dt,
Daniel Lezcano, Amit Kucheria, Matteo Croce, Andrew Morton,
Petr Mladek, Rafael J. Wysocki, Mike Rapoport, Josef Bacik,
Kai-Heng Feng, linux-pm
[-- Attachment #1: Type: text/plain, Size: 6684 bytes --]
The hardware shutdown function was exported from kernel/reboot for
other subsystems to use. Logic is copied from the thermal_core. The
protection mutex is replaced by an atomic_t to allow calls also from
an IRQ context. Also the WARN() was replaced by pr_emerg() based on
discussions here:
https://lore.kernel.org/lkml/YJuPwAZroVZ%2Fw633@alley/
and here:
https://lore.kernel.org/linux-iommu/20210331093104.383705-4-geert+renesas@glider.be/
Use the exported API instead of implementing own just for the
thermal_core.
Signed-off-by: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
---
Changelog:
v10:
- update commit message to mention changing WARN() to pr_emerg()
v9:
- Update the thermal documentation
v8:
- new patch (change added in v7, splitted in own patch at v8)
Use the exported API instead
---
.../driver-api/thermal/sysfs-api.rst | 24 +++----
drivers/thermal/thermal_core.c | 63 ++-----------------
2 files changed, 13 insertions(+), 74 deletions(-)
diff --git a/Documentation/driver-api/thermal/sysfs-api.rst b/Documentation/driver-api/thermal/sysfs-api.rst
index 4b638c14bc16..c93fa5e961a0 100644
--- a/Documentation/driver-api/thermal/sysfs-api.rst
+++ b/Documentation/driver-api/thermal/sysfs-api.rst
@@ -740,21 +740,15 @@ possible.
5. thermal_emergency_poweroff
=============================
-On an event of critical trip temperature crossing. Thermal framework
-allows the system to shutdown gracefully by calling orderly_poweroff().
-In the event of a failure of orderly_poweroff() to shut down the system
-we are in danger of keeping the system alive at undesirably high
-temperatures. To mitigate this high risk scenario we program a work
-queue to fire after a pre-determined number of seconds to start
-an emergency shutdown of the device using the kernel_power_off()
-function. In case kernel_power_off() fails then finally
-emergency_restart() is called in the worst case.
+On an event of critical trip temperature crossing the thermal framework
+shuts down the system by calling hw_protection_shutdown(). The
+hw_protection_shutdown() first attempts to perform an orderly shutdown
+but accepts a delay after which it proceeds doing a forced power-off
+or as last resort an emergency_restart.
The delay should be carefully profiled so as to give adequate time for
-orderly_poweroff(). In case of failure of an orderly_poweroff() the
-emergency poweroff kicks in after the delay has elapsed and shuts down
-the system.
+orderly poweroff.
-If set to 0 emergency poweroff will not be supported. So a carefully
-profiled non-zero positive value is a must for emergency poweroff to be
-triggered.
+If the delay is set to 0 emergency poweroff will not be supported. So a
+carefully profiled non-zero positive value is a must for emergency
+poweroff to be triggered.
diff --git a/drivers/thermal/thermal_core.c b/drivers/thermal/thermal_core.c
index d20b25f40d19..10a2d8e1cacf 100644
--- a/drivers/thermal/thermal_core.c
+++ b/drivers/thermal/thermal_core.c
@@ -36,10 +36,8 @@ static LIST_HEAD(thermal_governor_list);
static DEFINE_MUTEX(thermal_list_lock);
static DEFINE_MUTEX(thermal_governor_lock);
-static DEFINE_MUTEX(poweroff_lock);
static atomic_t in_suspend;
-static bool power_off_triggered;
static struct thermal_governor *def_governor;
@@ -327,70 +325,18 @@ static void handle_non_critical_trips(struct thermal_zone_device *tz, int trip)
def_governor->throttle(tz, trip);
}
-/**
- * thermal_emergency_poweroff_func - emergency poweroff work after a known delay
- * @work: work_struct associated with the emergency poweroff function
- *
- * This function is called in very critical situations to force
- * a kernel poweroff after a configurable timeout value.
- */
-static void thermal_emergency_poweroff_func(struct work_struct *work)
-{
- /*
- * We have reached here after the emergency thermal shutdown
- * Waiting period has expired. This means orderly_poweroff has
- * not been able to shut off the system for some reason.
- * Try to shut down the system immediately using kernel_power_off
- * if populated
- */
- WARN(1, "Attempting kernel_power_off: Temperature too high\n");
- kernel_power_off();
-
- /*
- * Worst of the worst case trigger emergency restart
- */
- WARN(1, "Attempting emergency_restart: Temperature too high\n");
- emergency_restart();
-}
-
-static DECLARE_DELAYED_WORK(thermal_emergency_poweroff_work,
- thermal_emergency_poweroff_func);
-
-/**
- * thermal_emergency_poweroff - Trigger an emergency system poweroff
- *
- * This may be called from any critical situation to trigger a system shutdown
- * after a known period of time. By default this is not scheduled.
- */
-static void thermal_emergency_poweroff(void)
+void thermal_zone_device_critical(struct thermal_zone_device *tz)
{
- int poweroff_delay_ms = CONFIG_THERMAL_EMERGENCY_POWEROFF_DELAY_MS;
/*
* poweroff_delay_ms must be a carefully profiled positive value.
- * Its a must for thermal_emergency_poweroff_work to be scheduled
+ * Its a must for forced_emergency_poweroff_work to be scheduled.
*/
- if (poweroff_delay_ms <= 0)
- return;
- schedule_delayed_work(&thermal_emergency_poweroff_work,
- msecs_to_jiffies(poweroff_delay_ms));
-}
+ int poweroff_delay_ms = CONFIG_THERMAL_EMERGENCY_POWEROFF_DELAY_MS;
-void thermal_zone_device_critical(struct thermal_zone_device *tz)
-{
dev_emerg(&tz->device, "%s: critical temperature reached, "
"shutting down\n", tz->type);
- mutex_lock(&poweroff_lock);
- if (!power_off_triggered) {
- /*
- * Queue a backup emergency shutdown in the event of
- * orderly_poweroff failure
- */
- thermal_emergency_poweroff();
- orderly_poweroff(true);
- power_off_triggered = true;
- }
- mutex_unlock(&poweroff_lock);
+ hw_protection_shutdown("Temperature too high", poweroff_delay_ms);
}
EXPORT_SYMBOL(thermal_zone_device_critical);
@@ -1538,7 +1484,6 @@ static int __init thermal_init(void)
ida_destroy(&thermal_cdev_ida);
mutex_destroy(&thermal_list_lock);
mutex_destroy(&thermal_governor_lock);
- mutex_destroy(&poweroff_lock);
return result;
}
postcore_initcall(thermal_init);
--
2.25.4
--
Matti Vaittinen, Linux device drivers
ROHM Semiconductors, Finland SWDC
Kiviharjunlenkki 1E
90220 OULU
FINLAND
~~~ "I don't think so," said Rene Descartes. Just then he vanished ~~~
Simon says - in Latin please.
~~~ "non cogito me" dixit Rene Descarte, deinde evanescavit ~~~
Thanks to Simon Glass for the translation =]
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply related [flat|nested] 7+ messages in thread
* Re: [PATCH RESEND v10 03/11] thermal: Use generic HW-protection shutdown API
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
0 siblings, 0 replies; 7+ messages in thread
From: Daniel Lezcano @ 2021-06-17 16:18 UTC (permalink / raw)
To: Matti Vaittinen, Matti Vaittinen
Cc: Mark Brown, Kees Cook, Andy Shevchenko, Zhang Rui, Guenter Roeck,
agross, devicetree, linux-power, linux-kernel, linux-renesas-soc,
linux-arm-msm, bjorn.andersson, lgirdwood, robh+dt,
Amit Kucheria, Matteo Croce, Andrew Morton, Petr Mladek,
Rafael J. Wysocki, Mike Rapoport, Josef Bacik, Kai-Heng Feng,
linux-pm
On 03/06/2021 07:41, Matti Vaittinen wrote:
> The hardware shutdown function was exported from kernel/reboot for
> other subsystems to use. Logic is copied from the thermal_core. The
> protection mutex is replaced by an atomic_t to allow calls also from
> an IRQ context. Also the WARN() was replaced by pr_emerg() based on
> discussions here:
> https://lore.kernel.org/lkml/YJuPwAZroVZ%2Fw633@alley/
> and here:
> https://lore.kernel.org/linux-iommu/20210331093104.383705-4-geert+renesas@glider.be/
>
> Use the exported API instead of implementing own just for the
> thermal_core.
>
> Signed-off-by: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
>
Acked-by: Daniel Lezcano <daniel.lezcano@linaro.org>
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH RESEND v10 00/11] Extend regulator notification support
2021-06-03 5:40 [PATCH RESEND v10 00/11] Extend regulator notification support Matti Vaittinen
2021-06-03 5:40 ` [PATCH RESEND v10 02/11] reboot: Add hardware protection power-off Matti Vaittinen
2021-06-03 5:41 ` [PATCH RESEND v10 03/11] thermal: Use generic HW-protection shutdown API Matti Vaittinen
@ 2021-06-17 12:37 ` Mark Brown
2021-06-21 18:45 ` Mark Brown
3 siblings, 0 replies; 7+ messages in thread
From: Mark Brown @ 2021-06-17 12:37 UTC (permalink / raw)
To: Matti Vaittinen
Cc: Matti Vaittinen, Kees Cook, Andy Shevchenko, Zhang Rui,
Guenter Roeck, agross, devicetree, linux-power, linux-kernel,
linux-renesas-soc, linux-arm-msm, bjorn.andersson, lgirdwood,
robh+dt, Daniel Lezcano, Amit Kucheria, Matteo Croce,
Andrew Morton, Petr Mladek, Rafael J. Wysocki, Mike Rapoport,
Josef Bacik, Kai-Heng Feng, linux-pm
[-- 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 --]
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH RESEND v10 00/11] Extend regulator notification support
2021-06-03 5:40 [PATCH RESEND v10 00/11] Extend regulator notification support Matti Vaittinen
` (2 preceding siblings ...)
2021-06-17 12:37 ` [PATCH RESEND v10 00/11] Extend regulator notification support Mark Brown
@ 2021-06-21 18:45 ` Mark Brown
3 siblings, 0 replies; 7+ messages in thread
From: Mark Brown @ 2021-06-21 18:45 UTC (permalink / raw)
To: Matti Vaittinen, Matti Vaittinen
Cc: Mark Brown, Matteo Croce, linux-kernel, robh+dt, bjorn.andersson,
Kees Cook, Daniel Lezcano, linux-arm-msm, Andrew Morton,
Andy Shevchenko, Guenter Roeck, Josef Bacik, linux-pm,
Mike Rapoport, Amit Kucheria, devicetree, Petr Mladek, Zhang Rui,
Kai-Heng Feng, lgirdwood, Rafael J. Wysocki, linux-renesas-soc,
agross, linux-power
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
^ permalink raw reply [flat|nested] 7+ messages in thread