From: Baoquan He <bhe@redhat.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, arnd@arndb.de,
hch@infradead.org, mcgrof@kernel.org
Subject: Re: [RFC PATCH 2/2] arch/*/io.h: remove ioremap_uc in some architectures
Date: Tue, 21 Feb 2023 19:38:09 +0800 [thread overview]
Message-ID: <Y/StIdIVz3iP00UP@MiWiFi-R3L-srv> (raw)
In-Reply-To: <CAMuHMdV4efVX8X1KoLJ-3pmzsxnU6TODw3b_37ZK771rfrqi7A@mail.gmail.com>
On 02/21/23 at 11:03am, Geert Uytterhoeven wrote:
> Hi Baoquan,
>
> Thanks for your patch!
>
> On Tue, Feb 21, 2023 at 7:36 AM Baoquan He <bhe@redhat.com> wrote:
> > ioremap_uc() is only meaningful on old x86-32 systems with the PAT
> > extension, and on ia64 with its slightly unconventional ioremap()
> > behavior, everywhere else this is the same as ioremap() anyway.
> >
> > So here, remove the ioremap_uc() definition in architecutures other
> > than x86 and ia64. These architectures all have asm-generic/io.h
> > included and will have the default ioremap_uc() definition which
> > returns NULL. If any ARCH really needs a specific ioremap_uc() for
>
> Please make it very clear that this changes existing behavior.
> At first, I had completely missed that.
Sure, I will update log.
>
> And of course the documentation should be updated to reflect that.
Makes sense, will do.
>
> > its own usage, one ioremap_uc() can be added in the ARH.
>
> s/ARH/ARCH/
Will update.
>
> > arch/m68k/include/asm/kmap.h | 1 -
>
> Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
Thanks for reviewing.
prev parent reply other threads:[~2023-02-21 11:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 6:07 [RFC PATCH 0/2] arch/*/io.h: remove ioremap_uc in some architectures Baoquan He
2023-02-21 6:07 ` [RFC PATCH 1/2] mips: add <asm-generic/io.h> including Baoquan He
2023-02-21 6:07 ` [RFC PATCH 2/2] arch/*/io.h: remove ioremap_uc in some architectures Baoquan He
2023-02-21 10:03 ` Geert Uytterhoeven
2023-02-21 11:38 ` Baoquan He [this message]
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=Y/StIdIVz3iP00UP@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mcgrof@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.