From: Jonathan Corbet <corbet@lwn.net>
To: Paul Walmsley <paul@pwsan.com>
Cc: Christoph Hellwig <hch@lst.de>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
Andreas Schwab <schwab@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH] Documentation: admin-guide: add earlycon documentation for RISC-V
Date: Tue, 12 Nov 2019 09:44:22 -0700 [thread overview]
Message-ID: <20191112094422.7abbc581@lwn.net> (raw)
In-Reply-To: <alpine.DEB.2.21.999.1911111729271.32333@utopia.booyaka.com>
On Mon, 11 Nov 2019 17:30:13 +0000 (UTC)
Paul Walmsley <paul@pwsan.com> wrote:
> On Fri, 8 Nov 2019, Christoph Hellwig wrote:
>
> > can you please revert this? The paragraph above this addition already
> > describes the riscv case perfecty well with my previous patch:
> >
> > earlycon= [KNL] Output early console device and options.
> >
> > When used with no options, the early console is
> > determined by stdout-path property in device tree's
> > chosen node or the ACPI SPCR table if supported by
> > the platform.
> >
> > [RISCV] When used with no options, the early
> > console is determined by the stdout-path
> > property in the device tree's chosen node.
>
> I support reverting the RISCV section, now that Christoph's more general
> change has gone in.
OK, the patch has been reverted.
Thanks,
jon
WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Corbet <corbet@lwn.net>
To: Paul Walmsley <paul@pwsan.com>
Cc: "open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
Andreas Schwab <schwab@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.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: Tue, 12 Nov 2019 09:44:22 -0700 [thread overview]
Message-ID: <20191112094422.7abbc581@lwn.net> (raw)
In-Reply-To: <alpine.DEB.2.21.999.1911111729271.32333@utopia.booyaka.com>
On Mon, 11 Nov 2019 17:30:13 +0000 (UTC)
Paul Walmsley <paul@pwsan.com> wrote:
> On Fri, 8 Nov 2019, Christoph Hellwig wrote:
>
> > can you please revert this? The paragraph above this addition already
> > describes the riscv case perfecty well with my previous patch:
> >
> > earlycon= [KNL] Output early console device and options.
> >
> > When used with no options, the early console is
> > determined by stdout-path property in device tree's
> > chosen node or the ACPI SPCR table if supported by
> > the platform.
> >
> > [RISCV] When used with no options, the early
> > console is determined by the stdout-path
> > property in the device tree's chosen node.
>
> I support reverting the RISCV section, now that Christoph's more general
> change has gone in.
OK, the patch has been reverted.
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-11-12 16:44 UTC|newest]
Thread overview: 14+ 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-09 19:53 ` Paul Walmsley
2019-10-10 7:10 ` Geert Uytterhoeven
2019-10-10 7:10 ` Geert Uytterhoeven
2019-10-10 17:23 ` Jonathan Corbet
2019-10-10 17:23 ` Jonathan Corbet
2019-11-08 6:10 ` Christoph Hellwig
2019-11-08 6:10 ` Christoph Hellwig
2019-11-11 17:30 ` Paul Walmsley
2019-11-11 17:30 ` Paul Walmsley
2019-11-12 16:44 ` Jonathan Corbet [this message]
2019-11-12 16:44 ` Jonathan Corbet
2019-10-17 16:10 ` Christoph Hellwig
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=20191112094422.7abbc581@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=paul@pwsan.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.