linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@sifive.com>
To: Christoph Hellwig <hch@lst.de>
Cc: schwab@suse.de, Christoph Hellwig <hch@lst.de>,
	Greg KH <gregkh@linuxfoundation.org>,
	jslaby@suse.com, linux-kernel@vger.kernel.org,
	linux-serial@vger.kernel.org,
	Paul Walmsley <paul.walmsley@sifive.com>,
	linux-riscv@lists.infradead.org
Subject: Re: [PATCH] serial/sifive: select SERIAL_EARLYCON
Date: Mon, 16 Sep 2019 09:12:09 -0700 (PDT)	[thread overview]
Message-ID: <mhng-671404fb-c86e-444a-86fb-b1ba027b1c36@palmer-si-x1c4> (raw)
In-Reply-To: <20190916064253.GA24654@lst.de>

On Sun, 15 Sep 2019 23:42:53 PDT (-0700), Christoph Hellwig wrote:
> On Fri, Sep 13, 2019 at 01:40:27PM -0700, Palmer Dabbelt wrote:
>> OpenEmbedded passes "earlycon=sbi", which I can find in the doumentation.
>> I can't find anything about just "earlycon".  I've sent a patch adding sbi
>> to the list of earlycon arguments.
>
> earlycon without arguments is documented, although just for ARM64.
> I can send a patch to update it to properly cover all DT platforms
> in addition.

Thanks.  I've kind of lost track of the thread, but assuming that does the 
"automatically pick an earlycon" stuff then that's probably what we should be 
using in the distros.

  reply	other threads:[~2019-09-16 16:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-10  5:59 [PATCH] serial/sifive: select SERIAL_EARLYCON Christoph Hellwig
2019-09-10  6:57 ` 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 [this message]
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=mhng-671404fb-c86e-444a-86fb-b1ba027b1c36@palmer-si-x1c4 \
    --to=palmer@sifive.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@lst.de \
    --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 \
    --cc=schwab@suse.de \
    /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).