From: Christoph Hellwig <hch@lst.de>
To: gregkh@linuxfoundation.org, jslaby@suse.com
Cc: paul.walmsley@sifive.com, linux-serial@vger.kernel.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH] serial/sifive: select SERIAL_EARLYCON
Date: Tue, 10 Sep 2019 07:59:23 +0200 [thread overview]
Message-ID: <20190910055923.28384-1-hch@lst.de> (raw)
The sifive serial driver implements earlycon support, but unless
another driver is built in that supports earlycon support it won't
be usable. Explicitly select SERIAL_EARLYCON instead.
Signed-off-by: Christoph Hellwig <hch@lst.de>
---
drivers/tty/serial/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/tty/serial/Kconfig b/drivers/tty/serial/Kconfig
index 530cb966092f..6b77a72278e3 100644
--- a/drivers/tty/serial/Kconfig
+++ b/drivers/tty/serial/Kconfig
@@ -1075,6 +1075,7 @@ config SERIAL_SIFIVE_CONSOLE
bool "Console on SiFive UART"
depends on SERIAL_SIFIVE=y
select SERIAL_CORE_CONSOLE
+ select SERIAL_EARLYCON
help
Select this option if you would like to use a SiFive UART as the
system console.
--
2.20.1
next reply other threads:[~2019-09-10 5:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 5:59 Christoph Hellwig [this message]
2019-09-10 6:57 ` [PATCH] serial/sifive: select SERIAL_EARLYCON Andreas Schwab
2019-09-10 7:05 ` Christoph Hellwig
2019-09-10 8:18 ` Andreas Schwab
2019-09-10 14:36 ` Christoph Hellwig
2019-09-10 14:42 ` Andreas Schwab
2019-09-13 20:40 ` Palmer Dabbelt
2019-09-16 6:42 ` Christoph Hellwig
2019-09-16 16:12 ` Palmer Dabbelt
2019-09-16 19:40 ` Andreas Schwab
2019-09-16 21:38 ` Palmer Dabbelt
2019-09-17 7:43 ` Andreas Schwab
2019-10-04 21:45 ` Atish Patra
2019-09-16 11:57 ` Paul Walmsley
2019-09-16 12:00 ` Andreas Schwab
2019-09-16 12:15 ` Christoph Hellwig
2019-09-16 12:18 ` Paul Walmsley
2019-09-16 12:22 ` Christoph Hellwig
2019-09-16 10:21 ` Paul Walmsley
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=20190910055923.28384-1-hch@lst.de \
--to=hch@lst.de \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=paul.walmsley@sifive.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).