[PATCH] docs: reboot: remove extra whitespace in reboot.c

Wojciech posted 1 patch 1 month, 2 weeks ago
kernel/reboot.c | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
[PATCH] docs: reboot: remove extra whitespace in reboot.c
Posted by Wojciech 1 month, 2 weeks ago
From 8d9e76d852aea428277a7a1c17056d2189b9a678 Mon Sep 17 00:00:00 2001
From: "Wojciech S." <wojciech.develop@gmail.com>
Date: Sat, 14 Feb 2026 18:08:11 +0100
Subject: [PATCH] docs: reboot: remove extra whitespace in reboot.c

Signed-off-by: Wojciech S. <wojciech.develop@gmail.com>
---
 kernel/reboot.c | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/kernel/reboot.c b/kernel/reboot.c
index ec087827c..7fcb3628d 100644
--- a/kernel/reboot.c
+++ b/kernel/reboot.c
@@ -41,8 +41,8 @@ static enum hw_protection_action
hw_protection_action = HWPROT_ACT_SHUTDOWN;
 /*
  * This variable is used privately to keep track of whether or not
  * reboot_type is still set to its default value (i.e., reboot= hasn't
- * been set on the command line).  This is needed so that we can
- * suppress DMI scanning for reboot quirks.  Without it, it's
+ * been set on the command line). This is needed so that we can
+ * suppress DMI scanning for reboot quirks. Without it, it's
  * impossible to override a faulty reboot quirk without recompiling.
  */
 int reboot_default = 1;
@@ -85,8 +85,8 @@ static BLOCKING_NOTIFIER_HEAD(reboot_notifier_list);
  * emergency_restart - reboot the system
  *
  * Without shutting down any hardware or taking any locks
- * reboot the system.  This is called when we know we are in
- * trouble so this is our best effort to reboot.  This is
+ * reboot the system. This is called when we know we are in
+ * trouble so this is our best effort to reboot. This is
  * safe to call in interrupt context.
  */
 void emergency_restart(void)
@@ -885,7 +885,7 @@ static int __orderly_poweroff(bool force)

  /*
  * I guess this should try to kick off some daemon to sync and
- * poweroff asap.  Or not even bother syncing if we're doing an
+ * poweroff asap. Or not even bother syncing if we're doing an
  * emergency shutdown?
  */
  emergency_sync();
-- 
2.47.3