Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Wed, 23 Jan 2019 11:56:01 -0800 (PST)
Subject:    Re: [PATCH v4 1/2] sh: mm: make use of new memblocks_present() helper
Message-ID: <mhng-96f28491-e123-459a-b09c-88732de06bbf@palmer-si-x1c4>
CC:     Christoph Hellwig <hch@infradead.org>, robh@kernel.org,
        dalias@libc.org, ysato@users.sourceforge.jp,
        linux-kernel@vger.kernel.org, sbates@raithlin.com,
        linux-riscv@lists.infradead.org, Christoph Hellwig <hch@lst.de>,
        dan.j.williams@intel.com
From:   Palmer Dabbelt <palmer@sifive.com>
To:     logang@deltatee.com
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Tue, 15 Jan 2019 09:30:44 PST (-0800), logang@deltatee.com wrote:
>
>
> On 2019-01-15 6:58 a.m., Christoph Hellwig wrote:
>> Reviewed-by: Christoph Hellwig <hch@lst.de>
>>
>> Probably no need to keep this in a series with the RISC-V code, this can
>> be queued up by the sh folks independently.
>
> Oh, yeah, sorry, I obviously didn't pay enough attention to this when I
> resent it. I sent the similar Arm changes to the appropriate list and,
> yes, the sh ones should go to that maintainer.
>
> @Palmer: if you can just look at taking the second patch, I'll resubmit
> the first one to the appropriate list.

Works for me.  I'll queue the second patch into my staging branch, targeted for
the next merge window.