From: Paul Walmsley <paul.walmsley@sifive.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Kevin Hilman <khilman@baylibre.com>,
Loys Ollivier <lollivier@baylibre.com>,
Palmer Dabbelt <palmer@sifive.com>,
linux-kernel@vger.kernel.org, Atish Patra <atish.patra@wdc.com>,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH] RISC-V: defconfig: enable clocks, serial console
Date: Mon, 17 Jun 2019 03:36:45 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.9999.1906170335140.19994@viisi.sifive.com> (raw)
In-Reply-To: <20190609075544.GA32207@infradead.org>
On Sun, 9 Jun 2019, Christoph Hellwig wrote:
> On Sat, Jun 08, 2019 at 06:49:09PM -0700, Paul Walmsley wrote:
> > On Wed, 5 Jun 2019, Kevin Hilman wrote:
> >
> > > Enable PRCI clock driver and serial console by default, so the default
> > > upstream defconfig is bootable to a serial console.
> > >
> > > Signed-off-by: Kevin Hilman <khilman@baylibre.com>
> >
> > Thanks, queued for v5.2-rc with Christoph's Reviewed-by:.
>
> To repeat myself: where do you apply it to? And could we please just
> have a shared maintainer tree on infradead.org or kernel.org so that
> people don't have to chase multiple trees to base their patches on?
As you requested last week, the shared tree announcement was posted as a
separate thread:
https://lore.kernel.org/linux-riscv/alpine.DEB.2.21.9999.1906170320300.19994@viisi.sifive.com/T/#u
- Paul
prev parent reply other threads:[~2019-06-17 10:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 17:50 [PATCH] RISC-V: defconfig: enable clocks, serial console Kevin Hilman
2019-06-06 8:57 ` Christoph Hellwig
2019-06-07 23:29 ` Kevin Hilman
2019-06-09 1:49 ` Paul Walmsley
2019-06-09 7:55 ` Christoph Hellwig
2019-06-17 10:36 ` 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.1906170335140.19994@viisi.sifive.com \
--to=paul.walmsley@sifive.com \
--cc=atish.patra@wdc.com \
--cc=hch@infradead.org \
--cc=khilman@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lollivier@baylibre.com \
--cc=palmer@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).