[PATCH 7/7] printk: Don't check for CON_ENABLED on console_unblank
Marcos Paulo de Souza
mpdesouza at suse.com
Fri Jun 6 19:53:49 PDT 2025
All consoles found on for_each_console_srcu are registered, meaning that all of
them are already CON_ENABLEDed.
Signed-off-by: Marcos Paulo de Souza <mpdesouza at suse.com>
---
kernel/printk/printk.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
index 658acf92aa3d2a3d1e294b7e17e5ee96d8169afe..8074a0f73691cfc5f637361048097ace1545c7c0 100644
--- a/kernel/printk/printk.c
+++ b/kernel/printk/printk.c
@@ -3360,7 +3360,7 @@ void console_unblank(void)
if (flags & CON_SUSPENDED)
continue;
- if ((flags & CON_ENABLED) && c->unblank) {
+ if (c->unblank) {
found_unblank = true;
break;
}
@@ -3402,7 +3402,7 @@ void console_unblank(void)
if (flags & CON_SUSPENDED)
continue;
- if ((flags & CON_ENABLED) && c->unblank)
+ if (c->unblank)
c->unblank();
}
console_srcu_read_unlock(cookie);
--
2.49.0
More information about the linux-um
mailing list