All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, arnd@arndb.de, hch@infradead.org,
	mcgrof@kernel.org, Baoquan He <bhe@redhat.com>
Subject: [RFC PATCH 0/2] arch/*/io.h: remove ioremap_uc in some architectures
Date: Tue, 21 Feb 2023 14:07:21 +0800	[thread overview]
Message-ID: <20230221060723.26291-1-bhe@redhat.com> (raw)

In a patchset reviewing, Arnd suggested removing arch specific ioremap_uc()
and using default one defined in asm-generic/io.h instead, other than
x86 and ia64. Please see below link for more details:

https://lore.kernel.org/all/056cc71f-7fb9-4d38-a442-a05de6f7d437@app.fastmail.com/T/#u

And Arnd also provided an old link where people earlier discussed this.

https://lore.kernel.org/all/20191111192258.2234502-1-arnd@arndb.de/

So in this patchset, I firstly add including asm-generic/io.h for mips,
then remove all arch specific ioremap_uc() definitions, except of x86
ans ia64. With the removing, those ARCH-es will have default
ioremap_uc() defined in asm-generic/io.h.

Baoquan He (2):
  mips: add <asm-generic/io.h> including
  arch/*/io.h: remove ioremap_uc in some architectures

 arch/alpha/include/asm/io.h    |  1 -
 arch/hexagon/include/asm/io.h  |  3 ---
 arch/m68k/include/asm/kmap.h   |  1 -
 arch/mips/include/asm/io.h     | 47 +++++++++++++++++++++++++++++++++-
 arch/mips/include/asm/mmiowb.h |  2 --
 arch/parisc/include/asm/io.h   |  2 --
 arch/powerpc/include/asm/io.h  |  1 -
 arch/sh/include/asm/io.h       |  2 --
 arch/sparc/include/asm/io_64.h |  1 -
 9 files changed, 46 insertions(+), 14 deletions(-)

-- 
2.34.1



             reply	other threads:[~2023-02-21  6:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-21  6:07 Baoquan He [this message]
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

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=20230221060723.26291-1-bhe@redhat.com \
    --to=bhe@redhat.com \
    --cc=arnd@arndb.de \
    --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.