From: Prarit Bhargava <prarit@redhat.com>
To: linux-fbdev@vger.kernel.org
Cc: Prarit Bhargava <prarit@redhat.com>,
Yisheng Xie <ysxie@foxmail.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Kees Cook <keescook@chromium.org>, Petr Mladek <pmladek@suse.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Steven Rostedt <rostedt@goodmis.org>,
Marko Myllynen <myllynen@redhat.com>,
Hans de Goede <hdegoede@redhat.com>,
dri-devel@lists.freedesktop.org,
Thierry Reding <treding@nvidia.com>
Subject: [PATCH v4 0/2] Do not output logo on quiet boots
Date: Thu, 10 Jan 2019 14:03:23 -0500 [thread overview]
Message-ID: <20190110190325.15241-1-prarit@redhat.com> (raw)
In-Reply-To: <20181030154419.2889-1-prarit@redhat.com>
On text-based systems the 'quiet' boot option will show printk levels
higher than CONSOLE_LOGLEVEL_QUIET. The displaying of the Tux logo
during boot can cause some consoles to lose display data and as a result
confuse the end user.
Do not display the Tux logo on systems that are in 'quiet' boot.
v2: It helps to commit all my changes before sending them. Remove extra
bracket.
v3: buildbot error fix: fbcon can be built as part of a module so export console_printk
v4: move console_printk change to separate patch, and drop logo cleanup
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: Hans de Goede <hdegoede@redhat.com>
Cc: Marko Myllynen <myllynen@redhat.com>
Cc: Steven Rostedt (VMware) <rostedt@goodmis.org>
Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: Kees Cook <keescook@chromium.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Thierry Reding <treding@nvidia.com>
Cc: Yisheng Xie <ysxie@foxmail.com>
Cc: Petr Mladek <pmladek@suse.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Prarit Bhargava (2):
fbcon: Silence fbcon logo on 'quiet' boots
printk: Export console_printk
drivers/video/fbdev/core/fbcon.c | 11 ++++++++---
kernel/printk/printk.c | 1 +
2 files changed, 9 insertions(+), 3 deletions(-)
--
2.17.2
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-01-10 19:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20181030154456epcas4p19e91c78daad3f1f48e8260601e5fdfec@epcas4p1.samsung.com>
2018-10-30 15:44 ` [PATCH v3] fbcon: Silence fbcon logo on 'quiet' boots Prarit Bhargava
2018-10-30 21:35 ` Steven Rostedt
2018-10-30 21:35 ` Steven Rostedt
2018-10-30 22:31 ` Prarit Bhargava
2018-12-20 16:31 ` Bartlomiej Zolnierkiewicz
2019-01-02 16:05 ` Petr Mladek
2019-01-03 10:38 ` Geert Uytterhoeven
2019-01-10 18:46 ` Prarit Bhargava
2019-01-07 10:09 ` Sergey Senozhatsky
2019-01-10 19:03 ` Prarit Bhargava [this message]
2019-01-10 19:03 ` [PATCH v4 1/2] " Prarit Bhargava
2019-01-11 6:04 ` Sergey Senozhatsky
2019-01-15 15:09 ` Petr Mladek
2019-01-10 19:03 ` [PATCH v4 2/2] printk: Export console_printk Prarit Bhargava
2019-01-11 6:02 ` Sergey Senozhatsky
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=20190110190325.15241-1-prarit@redhat.com \
--to=prarit@redhat.com \
--cc=b.zolnierkie@samsung.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hdegoede@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=myllynen@redhat.com \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=treding@nvidia.com \
--cc=ysxie@foxmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox