From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Baoquan He <bhe@redhat.com>
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 11:03:14 +0100 [thread overview]
Message-ID: <CAMuHMdV4efVX8X1KoLJ-3pmzsxnU6TODw3b_37ZK771rfrqi7A@mail.gmail.com> (raw)
In-Reply-To: <20230221060723.26291-3-bhe@redhat.com>
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.
And of course the documentation should be updated to reflect that.
> its own usage, one ioremap_uc() can be added in the ARH.
s/ARH/ARCH/
> arch/m68k/include/asm/kmap.h | 1 -
Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2023-02-21 10:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 6:07 [RFC PATCH 0/2] " 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 [this message]
2023-02-21 11:38 ` Baoquan He
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=CAMuHMdV4efVX8X1KoLJ-3pmzsxnU6TODw3b_37ZK771rfrqi7A@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=arnd@arndb.de \
--cc=bhe@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox