From: Palmer Dabbelt <palmer@sifive.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-riscv@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, linux-sh@vger.kernel.org,
sbates@raithlin.com, aou@eecs.berkeley.edu,
Christoph Hellwig <hch@lst.de>,
akpm@linux-foundation.org, Arnd Bergmann <arnd@arndb.de>,
logang@deltatee.com
Subject: Re: [PATCH v2 0/6] sparsemem support for RISC-V
Date: Mon, 15 Oct 2018 17:04:15 -0700 (PDT) [thread overview]
Message-ID: <mhng-fd0541de-3ac1-4772-916d-be6b2d02e63e@palmer-si-x1c4> (raw)
In-Reply-To: <20181015175702.9036-1-logang@deltatee.com>
On Mon, 15 Oct 2018 10:56:56 PDT (-0700), logang@deltatee.com wrote:
> This patchset implements sparsemem on RISC-V. The first few patches
> move some code in existing architectures into common helpers
> so they can be used by the new RISC-V implementation. The final
> patch actually adds sparsmem support to RISC-V.
>
> This is the first small step in supporting P2P on RISC-V.
Thanks. I see less maintainer tags for the parts that touch other ports than I
would feel comfortable merging. I'm going to let this sit in my inbox for
a bit and we'll see if anything collects.
For patch sets I submit that clean up other ports I've attempted to split the
patch into N patch sets, where:
* One part adds the generic support, which starts out as dead code.
* One part per arch uses the generic support.
This is a bit of a headache, but it at least allows us to get the RISC-V
version that uses the generic support in quickly while waiting on acks from the
other arch maintainers.
Like I said, I'll wait a bit and hope people ack.
Thanks!
prev parent reply other threads:[~2018-10-16 0:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 17:56 Logan Gunthorpe
2018-10-15 17:56 ` [PATCH v2 1/6] mm: Introduce common STRUCT_PAGE_MAX_SHIFT define Logan Gunthorpe
2018-10-29 17:53 ` Will Deacon
2018-10-15 17:56 ` [PATCH v2 2/6] mm/sparse: add common helper to mark all memblocks present Logan Gunthorpe
2018-10-15 17:56 ` [PATCH v2 3/6] ARM: mm: make use of new memblocks_present() helper Logan Gunthorpe
2018-10-15 17:57 ` [PATCH v2 4/6] arm64: " Logan Gunthorpe
2018-10-15 17:57 ` [PATCH v2 5/6] sh: " Logan Gunthorpe
2018-10-15 17:57 ` [PATCH v2 6/6] RISC-V: Implement sparsemem Logan Gunthorpe
2018-12-17 14:59 ` Nick Kossifidis
2018-12-17 16:50 ` Logan Gunthorpe
2018-10-16 0:04 ` Palmer Dabbelt [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=mhng-fd0541de-3ac1-4772-916d-be6b2d02e63e@palmer-si-x1c4 \
--to=palmer@sifive.com \
--cc=akpm@linux-foundation.org \
--cc=aou@eecs.berkeley.edu \
--cc=arnd@arndb.de \
--cc=hch@lst.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-sh@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=sbates@raithlin.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