From: Paul Walmsley <paul.walmsley@sifive.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Andreas Schwab <schwab@suse.de>, Jonathan Corbet <corbet@lwn.net>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"open list:SERIAL DRIVERS" <linux-serial@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] Documentation: admin-guide: add earlycon documentation for the sifive serial driver
Date: Wed, 9 Oct 2019 07:31:16 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.9999.1910090720290.11044@viisi.sifive.com> (raw)
In-Reply-To: <CAMuHMdVh=CUXKwnXee067cRccVBDVuwWpo1wP7crAaCFA=y2Tw@mail.gmail.com>
Hi Geert,
On Wed, 9 Oct 2019, Geert Uytterhoeven wrote:
> On Wed, Oct 9, 2019 at 12:06 PM Andreas Schwab <schwab@suse.de> wrote:
> > On Okt 09 2019, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > > I believe risc-v is DT-only, so if chosen/stdout-path is set up
> >
> > If. Currently, it isn't.
>
> IC. So isn't it better to fix that, instead of pointing people to more obscure
> legacy solutions?
There's nothing that's RISC-V specific about the SiFive serial IP or
its driver. So the issue of whether RISC-V is DT-only or not probably
shouldn't impact whether we document that the SiFive serial driver
supports earlycon.
best regards,
- Paul
prev parent reply other threads:[~2019-10-09 14:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 23:08 Paul Walmsley
2019-10-09 6:56 ` Geert Uytterhoeven
2019-10-09 10:06 ` Andreas Schwab
2019-10-09 10:55 ` Geert Uytterhoeven
2019-10-09 14:31 ` Paul Walmsley [this message]
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=alpine.DEB.2.21.9999.1910090720290.11044@viisi.sifive.com \
--to=paul.walmsley@sifive.com \
--cc=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-serial@vger.kernel.org \
--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
all inboxes | Powered by JetHome®