All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
	linux-mm@kvack.org, arnd@arndb.de, geert@linux-m68k.org,
	hch@infradead.org
Subject: Re: [PATCH v2 0/2] arch/*/io.h: remove ioremap_uc in some architectures
Date: Fri, 3 Mar 2023 18:24:50 +0800	[thread overview]
Message-ID: <ZAHK8kvYzrZfvyBo@MiWiFi-R3L-srv> (raw)
In-Reply-To: <ZAD/jLaacr0Xu+/M@bombadil.infradead.org>

On 03/02/23 at 11:57am, Luis Chamberlain wrote:
> On Wed, Mar 01, 2023 at 06:22:06PM +0800, Baoquan He wrote:
> > This patchset tries to remove ioremap_uc() in the current architectures
> > except of x86 and ia64. They will use the default ioremap_uc definition
> > in <asm-generic/io.h> which returns NULL.
> > 
> > If any arch sees a breakage caused by the default ioremap_uc(), it can
> > provide a sepcific one for its own usage.
> 
> Feel free to add:
> 
> Reviewed-by: Luis Chamberlain <mcgrof@kernel.org>

Thanks for check. I made some changes according to comments, will repost.
Please help review.


      reply	other threads:[~2023-03-03 10:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-01 10:22 [PATCH v2 0/2] arch/*/io.h: remove ioremap_uc in some architectures Baoquan He
2023-03-01 10:22 ` [PATCH v2 1/2] mips: add <asm-generic/io.h> including Baoquan He
2023-03-01 14:06   ` Arnd Bergmann
2023-03-02  4:12     ` Baoquan He
2023-03-02  7:12       ` Arnd Bergmann
2023-03-02  9:09         ` Baoquan He
2023-03-03  9:13         ` Baoquan He
2023-03-01 10:22 ` [PATCH v2 2/2] arch/*/io.h: remove ioremap_uc in some architectures Baoquan He
2023-03-01 13:37 ` [PATCH v2 0/2] " Baoquan He
2023-03-02 19:57 ` Luis Chamberlain
2023-03-03 10:24   ` 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=ZAHK8kvYzrZfvyBo@MiWiFi-R3L-srv \
    --to=bhe@redhat.com \
    --cc=arnd@arndb.de \
    --cc=geert@linux-m68k.org \
    --cc=hch@infradead.org \
    --cc=linux-arch@vger.kernel.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.