[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <mhng-d8f1905a-8985-4797-b05b-b165b4ce91f1@palmer-si-x1c4>
Date: Mon, 15 Oct 2018 10:39:29 -0700 (PDT)
From: Palmer Dabbelt <palmer@...ive.com>
To: sbates@...thlin.com
CC: logang@...tatee.com, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, linux-riscv@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, linux-sh@...r.kernel.org,
aou@...s.berkeley.edu, Christoph Hellwig <hch@....de>,
logang@...tatee.com, Andrew Waterman <andrew@...ive.com>,
Olof Johansson <olof@...om.net>,
Michael Clark <michaeljclark@....com>, robh@...nel.org,
zong@...estech.com
Subject: Re: [PATCH 5/5] RISC-V: Implement sparsemem
On Thu, 11 Oct 2018 05:18:20 PDT (-0700), sbates@...thlin.com wrote:
> Palmer
>
>> I don't really know anything about this, but you're welcome to add a
>>
>> Reviewed-by: Palmer Dabbelt <palmer@...ive.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 ;-)
Powered by blists - more mailing lists