[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87jzzt1ioc.fsf@mpe.ellerman.id.au>
Date: Tue, 07 Mar 2023 11:58:27 +1100
From: Michael Ellerman <mpe@...erman.id.au>
To: Arnd Bergmann <arnd@...db.de>,
Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Linux-Arch <linux-arch@...r.kernel.org>,
Baoquan He <bhe@...hat.com>, linux-sh@...r.kernel.org,
linux-m68k@...ts.linux-m68k.org, linux-hexagon@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mips@...r.kernel.org,
Christoph Hellwig <hch@...radead.org>, linux-mm@...ck.org,
Luis Chamberlain <mcgrof@...nel.org>,
linux-parisc@...r.kernel.org, linux-alpha@...r.kernel.org,
sparclinux@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org
Subject: Re: [PATCH v3 2/2] arch/*/io.h: remove ioremap_uc in some
architectures
"Arnd Bergmann" <arnd@...db.de> writes:
> On Sun, Mar 5, 2023, at 10:29, Geert Uytterhoeven wrote:
>> On Sun, Mar 5, 2023 at 10:23 AM Michael Ellerman <mpe@...erman.id.au> wrote:
>>> Maybe that exact code path is only reachable on x86/ia64? But if so
>>> please explain why.
>>>
>>> Otherwise it looks like this series could break that driver on powerpc
>>> at least.
>>
>> Indeed.
>
> When I last looked into this, I sent a patch to use ioremap()
> on non-x86:
>
> https://lore.kernel.org/all/20191111192258.2234502-1-arnd@arndb.de/
OK thanks.
Baoquan can you add that patch to the start of this series if/when you
post the next version?
cheers
Powered by blists - more mailing lists