From: Thierry Reding <treding@nvidia.com>
To: Prarit Bhargava <prarit@redhat.com>
Cc: Yisheng Xie <ysxie@foxmail.com>,
linux-fbdev@vger.kernel.org, Kees Cook <keescook@chromium.org>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
dri-devel@lists.freedesktop.org,
Marko Myllynen <myllynen@redhat.com>,
Hans de Goede <hdegoede@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH] fbcon: Silence fbcon logo on 'quiet' boots
Date: Mon, 29 Oct 2018 15:24:20 +0000 [thread overview]
Message-ID: <20181029152419.GB30162@ulmo> (raw)
In-Reply-To: <20181029130232.31661-1-prarit@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1845 bytes --]
On Mon, Oct 29, 2018 at 09:02:32AM -0400, Prarit Bhargava wrote:
> A variant of this patch has been in Fedora since at least 2010 and
> AFAWCT there haven't been any complaints about the change in behavior.
>
> https://src.fedoraproject.org/cgit/rpms/kernel.git/tree/silence-fbcon-logo.patch
>
> P.
>
> ---8<---
>
> 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.
>
> Signed-off-by: Prarit Bhargava <prarit@redhat.com>
> Cc: Hans de Goede <hdegoede@redhat.com>
> Cc: Marko Myllynen <myllynen@redhat.com>
> 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: dri-devel@lists.freedesktop.org
> Cc: Steven Rostedt (VMware) <rostedt@goodmis.org>
> ---
> drivers/video/fbdev/core/fbcon.c | 13 ++++++++-----
> 1 file changed, 8 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/video/fbdev/core/fbcon.c b/drivers/video/fbdev/core/fbcon.c
> index 75ebbbf0a1fb..a2f2c7ea11ef 100644
> --- a/drivers/video/fbdev/core/fbcon.c
> +++ b/drivers/video/fbdev/core/fbcon.c
> @@ -650,11 +650,14 @@ static void fbcon_prepare_logo(struct vc_data *vc, struct fb_info *info,
> kfree(save);
> }
>
> + if (logo_shown == FBCON_LOGO_DONTSHOW) {
> + return;
> +
You're missing a closing } here (well, you really shouldn't have the
opening { in the first place since this is a single line block.
That's what's causing the warnings from the 0-day builder.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-10-29 15:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 13:02 [PATCH] fbcon: Silence fbcon logo on 'quiet' boots Prarit Bhargava
2018-10-29 13:56 ` kbuild test robot
2018-10-29 15:15 ` Prarit Bhargava
2018-11-12 3:18 ` [kbuild-all] " Rong Chen
2018-11-12 13:52 ` Prarit Bhargava
2018-10-29 13:57 ` kbuild test robot
2018-10-29 15:24 ` Thierry Reding [this message]
2018-10-29 15:30 ` Prarit Bhargava
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=20181029152419.GB30162@ulmo \
--to=treding@nvidia.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=prarit@redhat.com \
--cc=rostedt@goodmis.org \
--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;
as well as URLs for NNTP newsgroup(s).