From: Jonathan Corbet <corbet@lwn.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
Andreas Schwab <schwab@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
linux-riscv@lists.infradead.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] Documentation: admin-guide: add earlycon documentation for RISC-V
Date: Thu, 10 Oct 2019 11:23:47 -0600 [thread overview]
Message-ID: <20191010112347.4a7237bb@lwn.net> (raw)
In-Reply-To: <CAMuHMdUfqvkVJHHwyuYxLSxj_iUofx-vSvEj92C5mg3bGxHqmA@mail.gmail.com>
On Thu, 10 Oct 2019 09:10:18 +0200
Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> On Wed, Oct 9, 2019 at 9:53 PM Paul Walmsley <paul.walmsley@sifive.com> wrote:
> > Kernels booting on RISC-V can specify "earlycon" with no options on
> > the Linux command line, and the generic DT earlycon support will query
> > the "chosen/stdout-path" property (if present) to determine which
> > early console device to use. Document this appropriately in the
> > admin-guide.
> >
> > Signed-off-by: Paul Walmsley <paul.walmsley@sifive.com>
>
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
Applied, thanks.
jon
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-10-10 17:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 19:53 [PATCH] Documentation: admin-guide: add earlycon documentation for RISC-V Paul Walmsley
2019-10-10 7:10 ` Geert Uytterhoeven
2019-10-10 17:23 ` Jonathan Corbet [this message]
2019-11-08 6:10 ` Christoph Hellwig
2019-11-11 17:30 ` Paul Walmsley
2019-11-12 16:44 ` Jonathan Corbet
2019-10-17 16:10 ` Christoph Hellwig
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=20191010112347.4a7237bb@lwn.net \
--to=corbet@lwn.net \
--cc=geert@linux-m68k.org \
--cc=hch@lst.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.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).