From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752169AbdJYMsG (ORCPT ); Wed, 25 Oct 2017 08:48:06 -0400 Received: from mx2.suse.de ([195.135.220.15]:36164 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751835AbdJYMqb (ORCPT ); Wed, 25 Oct 2017 08:46:31 -0400 From: Max Staudt To: b.zolnierkie@samsung.com, linux-fbdev@vger.kernel.org Cc: mstaudt@suse.de, tiwai@suse.com, oneukum@suse.com, msrb@suse.com, sndirsch@suse.com, michal@markovi.net, linux-kernel@vger.kernel.org Subject: [RFC 06/14] bootsplash: Disable on SysRq SAK Date: Wed, 25 Oct 2017 14:45:54 +0200 Message-Id: <20171025124602.28292-7-mstaudt@suse.de> X-Mailer: git-send-email 2.12.3 In-Reply-To: <20171025124602.28292-1-mstaudt@suse.de> References: <20171025124602.28292-1-mstaudt@suse.de> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org When the user requests a clean TTY via the SAK SysRq, that means he really wants to use the console. Let's disable the bootsplash, even if the request is not on a VT, as the user probably knows what he's doing and it's more helpful to get out of his way. Signed-off-by: Max Staudt Reviewed-by: Oliver Neukum --- drivers/tty/sysrq.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/tty/sysrq.c b/drivers/tty/sysrq.c index 3ffc1ce29023..bc6a24c9dfa8 100644 --- a/drivers/tty/sysrq.c +++ b/drivers/tty/sysrq.c @@ -49,6 +49,7 @@ #include #include #include +#include #include #include @@ -104,6 +105,8 @@ static void sysrq_handle_SAK(int key) { struct work_struct *SAK_work = &vc_cons[fg_console].SAK_work; schedule_work(SAK_work); + + bootsplash_disable(); } static struct sysrq_key_op sysrq_SAK_op = { .handler = sysrq_handle_SAK, -- 2.12.3