From: Palmer Dabbelt <palmer@sifive.com>
To: sbates@raithlin.com
Cc: logang@deltatee.com, 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,
aou@eecs.berkeley.edu,
Christoph Hellwig <hch@lst.de>logang@deltatee.com,
Andrew Waterman <andrew@sifive.com>,
Olof Johansson <olof@lixom.net>,
Michael Clark <michaeljclark@mac.com>,
robh@kernel.org, zong@andestech.com
Subject: Re: [PATCH 5/5] RISC-V: Implement sparsemem
Date: Mon, 15 Oct 2018 10:39:29 -0700 (PDT) [thread overview]
Message-ID: <mhng-d8f1905a-8985-4797-b05b-b165b4ce91f1@palmer-si-x1c4> (raw)
In-Reply-To: <15C8B877-4BBE-47E1-98D1-945E9355E757@raithlin.com>
On Thu, 11 Oct 2018 05:18:20 PDT (-0700), sbates@raithlin.com wrote:
> Palmer
>
>> I don't really know anything about this, but you're welcome to add a
>>
>> Reviewed-by: Palmer Dabbelt <palmer@sifive.com>
>
> Thanks. I think it would be good to get someone who's familiar with linux/mm to take a look.
>
>> if you think it'll help. I'm assuming you're targeting a different tree for
>> the patch set, in which case it's probably best to keep this together with the
>> rest of it.
>
> No I think this series should be pulled by the RISC-V maintainer. The other patches in this series just refactor some code and need to be ACK'ed by their ARCH developers but I suspect the series should be pulled into RISC-V. That said since it does touch other arch should it be pulled by mm?
>
> BTW note that RISC-V SPARSEMEM support is pretty useful for all manner of things and not just the p2pdma discussed in the cover.
Ah, OK -- I thought this was adding the support everywhere. Do you mind
re-sending the patches with the various acks/reviews and I'll put in on
for-next?
>
>> Thanks for porting your stuff to RISC-V!
>
> You bet ;-)
next prev parent reply other threads:[~2018-10-15 17:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 16:16 [PATCH 0/5] sparsemem support for RISC-V Logan Gunthorpe
2018-10-05 16:16 ` [PATCH 1/5] mm/sparse: add common helper to mark all memblocks present Logan Gunthorpe
2018-10-11 13:30 ` Christoph Hellwig
2018-10-05 16:16 ` [PATCH 2/5] ARM: mm: make use of new memblocks_present() helper Logan Gunthorpe
2018-10-05 16:16 ` [PATCH 3/5] arm64: " Logan Gunthorpe
2018-10-05 16:32 ` Catalin Marinas
2018-10-05 16:16 ` [PATCH 4/5] sh: " Logan Gunthorpe
2018-10-05 16:16 ` [PATCH 5/5] RISC-V: Implement sparsemem Logan Gunthorpe
2018-10-11 0:27 ` Palmer Dabbelt
2018-10-11 12:18 ` Stephen Bates
2018-10-15 17:39 ` Palmer Dabbelt [this message]
2018-10-11 13:37 ` Christoph Hellwig
2018-10-11 16:24 ` Logan Gunthorpe
2018-10-11 17:30 ` Logan Gunthorpe
2018-10-11 18:45 ` Logan Gunthorpe
2018-10-11 20:21 ` Logan Gunthorpe
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-d8f1905a-8985-4797-b05b-b165b4ce91f1@palmer-si-x1c4 \
--to=palmer@sifive.com \
--cc=aou@eecs.berkeley.edu \
--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