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:   Mon, 2 Dec 2019 18:52:42 -0800 (PST)
From:   Paul Walmsley <paul.walmsley@sifive.com>
To:     Linus Torvalds <torvalds@linux-foundation.org>
cc:     Christoph Hellwig <hch@infradead.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] generic ioremap for 5.5
In-Reply-To: <CAHk-=whpKDQze+kcCw5e-TK2J4T9-qACQ_o7XAtTO+dD+FJOsw@mail.gmail.com>
Message-ID: <alpine.DEB.2.21.9999.1912021851400.56420@viisi.sifive.com>
References: <20191125192758.GA13913@infradead.org> <CAHk-=whpKDQze+kcCw5e-TK2J4T9-qACQ_o7XAtTO+dD+FJOsw@mail.gmail.com>
User-Agent: Alpine 2.21.9999 (DEB 301 2018-08-15)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Thu, 28 Nov 2019, Linus Torvalds wrote:

> On Mon, Nov 25, 2019 at 11:28 AM Christoph Hellwig <hch@infradead.org> wrote:
> >
> > There are two conflicts with the riscv tree - one is a trivial makefile
> > context one with the nommu support, and the other is the split of the
> > riscv <asm/io.h> which means that the removals in this pull request need
> > to be applied to the new location that they were moved to in the riscv
> > tree.
> 
> The conflict was trivial to fix up, but since I don't do RISC-V
> cross-builds, I'd like PaulW to please check that there weren't any
> surprising semantic issues too - or that I didn't mess up.
> 
> Paul? (It's not actually pushed out yet, it's still building, but the
> ioremap merge should be there in a moment)

Looks good to me, and passes basic tests with both QEMU and hardware.  

thanks,

- Paul