public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm•com>
To: Baoquan He <bhe@redhat•com>
Cc: linux-kernel@vger•kernel.org, linux-arch@vger•kernel.org,
	linux-mm@kvack•org, arnd@arndb•de, christophe.leroy@csgroup•eu,
	hch@lst•de, rppt@kernel•org, willy@infradead•org,
	agordeev@linux•ibm.com, wangkefeng.wang@huawei•com,
	schnelle@linux•ibm.com, David.Laight@aculab•com,
	shorne@gmail•com, deller@gmx•de, Will Deacon <will@kernel•org>,
	linux-arm-kernel@lists•infradead.org
Subject: Re: [PATCH v6 18/19] arm64 : mm: add wrapper function ioremap_prot()
Date: Wed, 14 Jun 2023 16:14:10 +0100	[thread overview]
Message-ID: <ZInZQnhD2EfZbamK@arm.com> (raw)
In-Reply-To: <20230609075528.9390-19-bhe@redhat.com>

On Fri, Jun 09, 2023 at 03:55:27PM +0800, Baoquan He wrote:
> Since hook functions ioremap_allowed() and iounmap_allowed() will be
> obsoleted, add wrapper function ioremap_prot() to contain the
> specific handling in addition to generic_ioremap_prot() invocation.
> 
> Signed-off-by: Baoquan He <bhe@redhat•com>
> Reviewed-by: Christoph Hellwig <hch@lst•de>
> Reviewed-by: Kefeng Wang <wangkefeng.wang@huawei•com>
> Reviewed-by: Mike Rapoport (IBM) <rppt@kernel•org>
> Cc: Catalin Marinas <catalin.marinas@arm•com>
> Cc: Will Deacon <will@kernel•org>
> Cc: linux-arm-kernel@lists•infradead.org

Acked-by: Catalin Marinas <catalin.marinas@arm•com>

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2023-06-14 15:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230609075528.9390-1-bhe@redhat.com>
2023-06-09  7:55 ` [PATCH v6 18/19] arm64 : mm: add wrapper function ioremap_prot() Baoquan He
2023-06-14 15:14   ` Catalin Marinas [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=ZInZQnhD2EfZbamK@arm.com \
    --to=catalin.marinas@arm$(echo .)com \
    --cc=David.Laight@aculab$(echo .)com \
    --cc=agordeev@linux$(echo .)ibm.com \
    --cc=arnd@arndb$(echo .)de \
    --cc=bhe@redhat$(echo .)com \
    --cc=christophe.leroy@csgroup$(echo .)eu \
    --cc=deller@gmx$(echo .)de \
    --cc=hch@lst$(echo .)de \
    --cc=linux-arch@vger$(echo .)kernel.org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-mm@kvack$(echo .)org \
    --cc=rppt@kernel$(echo .)org \
    --cc=schnelle@linux$(echo .)ibm.com \
    --cc=shorne@gmail$(echo .)com \
    --cc=wangkefeng.wang@huawei$(echo .)com \
    --cc=will@kernel$(echo .)org \
    --cc=willy@infradead$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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