From: Paul Walmsley <paul.walmsley@sifive.com>
To: Alexandre Ghiti <alex@ghiti.fr>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: kbuild: add virtual memory system selection
Date: Wed, 7 Aug 2019 09:42:27 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.9999.1908070940110.13971@viisi.sifive.com> (raw)
In-Reply-To: <c331e389-5f33-634a-f62f-e48251ca4cfe@ghiti.fr>
On Wed, 7 Aug 2019, Alexandre Ghiti wrote:
> And FYI my series and your patch are already in linux-next.
Yes, I agree with Christoph that it would be preferable not to break
randconfig/allyesconfig. So if you don't mind, could you respin the
RISC-V patch to drop the Sv48 portion, and simply assume Sv39 for RV64 as
we do for the rest of the RISC-V kernel code? We can always add Sv48
back in later.
If you agree, then once you do that, I'll ask Andrew to drop the RISC-V
Kbuild patch that he's carrying.
- Paul
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2019-08-07 16:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 20:00 [PATCH] riscv: kbuild: add virtual memory system selection Paul Walmsley
2019-07-28 13:38 ` Bin Meng
2019-07-31 19:37 ` Paul Walmsley
2019-08-01 8:56 ` Bin Meng
2019-08-02 8:44 ` Christoph Hellwig
2019-08-07 0:02 ` Paul Walmsley
2019-08-07 5:42 ` Christoph Hellwig
2019-08-07 7:04 ` Alexandre Ghiti
2019-08-07 15:12 ` Christoph Hellwig
2019-08-07 16:20 ` Palmer Dabbelt
2019-08-07 16:42 ` 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.1908070940110.13971@viisi.sifive.com \
--to=paul.walmsley@sifive.com \
--cc=alex@ghiti.fr \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
/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).