From: Jiri Slaby <jslaby@suse.cz>
To: Matthew Leach <matthew.leach@codethink.co.uk>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kernel@lists.codethink.co.uk
Subject: Re: [PATCH] tty: serial: 8250: add CON_CONSDEV to flags
Date: Tue, 18 Oct 2016 18:15:44 +0200 [thread overview]
Message-ID: <40b80b82-531d-d9e8-0b4d-bdd559ad5044@suse.cz> (raw)
In-Reply-To: <1466522389-26943-1-git-send-email-matthew.leach@codethink.co.uk>
On 06/21/2016, 05:19 PM, Matthew Leach wrote:
> When using the 8250 as a boot console and the main console results in
> messages being printed twice. The console framework will only
> unregister boot consoles if a new console is registered with the
> CON_CONSDEV flag set.
>
> Set this flag for the univ8250 console to prevent double-registration.
>
> Signed-off-by: Matthew Leach <matthew.leach@codethink.co.uk>
> ---
> drivers/tty/serial/8250/8250_core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/tty/serial/8250/8250_core.c b/drivers/tty/serial/8250/8250_core.c
> index 2f4f5ee..7a7453d 100644
> --- a/drivers/tty/serial/8250/8250_core.c
> +++ b/drivers/tty/serial/8250/8250_core.c
> @@ -675,7 +675,7 @@ static struct console univ8250_console = {
> .device = uart_console_device,
> .setup = univ8250_console_setup,
> .match = univ8250_console_match,
> - .flags = CON_PRINTBUFFER | CON_ANYTIME,
> + .flags = CON_PRINTBUFFER | CON_ANYTIME | CON_CONSDEV,
This patch breaks console= parameter handling. Passing:
console=ttyS0 console=tty0
no longer means /dev/console is tty0 and it should be as is documented.
I have not investigated further yet.
thanks,
--
js
suse labs
next prev parent reply other threads:[~2016-10-18 16:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 15:19 Matthew Leach
2016-10-18 16:15 ` Jiri Slaby [this message]
2016-10-18 16:23 ` [Linux-kernel] " Ben Dooks
2016-10-18 16:57 ` Jiri Slaby
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=40b80b82-531d-d9e8-0b4d-bdd559ad5044@suse.cz \
--to=jslaby@suse.cz \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@lists.codethink.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=matthew.leach@codethink.co.uk \
/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
all inboxes | Powered by JetHome®