linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Jinjiang Tu <tujinjiang@huawei.com>,
	akpm@linux-foundation.org, david@kernel.org,
	zengheng4@huawei.com, ryan.roberts@arm.com,
	anshuman.khandual@arm.com, wangkefeng.wang@huawei.com,
	linux-arm-kernel@lists.infradead.org, linux-mm@kvack.org
Subject: Re: [PATCH v3] arm64: mm: fix pass user prot to ioremap_prot in generic_access_phys
Date: Wed, 18 Feb 2026 16:22:20 +0000	[thread overview]
Message-ID: <aZXnPLt-Pkfj6eZl@willie-the-truck> (raw)
In-Reply-To: <aYnM1A-9VZaOZoC_@willie-the-truck>

On Mon, Feb 09, 2026 at 12:02:28PM +0000, Will Deacon wrote:
> I still think this is unnecessary churn. You then end up with
> ioremap_prot() having no callers outside of arch/ and if core code just
> defines ioremap_user_prot() to ioremap_prot() for everybody apart from
> arm64 then the intent isn't clear at all.

FWIW, I've had a crack at implementing this here:

https://git.kernel.org/pub/scm/linux/kernel/git/will/linux.git/log/?h=ioremap-prot

I can post the patches at -rc1.

Will


      reply	other threads:[~2026-02-18 16:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-30  7:38 Jinjiang Tu
2026-01-30 12:19 ` Catalin Marinas
2026-01-31  0:07   ` Jinjiang Tu
2026-02-02 14:55 ` Will Deacon
2026-02-03  3:38   ` Jinjiang Tu
2026-02-03  9:23     ` Will Deacon
2026-02-05  7:23       ` Jinjiang Tu
2026-02-05 14:31         ` Catalin Marinas
2026-02-05 17:36           ` Will Deacon
2026-02-05 18:25             ` Catalin Marinas
2026-02-06 12:08               ` Catalin Marinas
2026-02-09 12:02                 ` Will Deacon
2026-02-18 16:22                   ` Will Deacon [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=aZXnPLt-Pkfj6eZl@willie-the-truck \
    --to=will@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=anshuman.khandual@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=david@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mm@kvack.org \
    --cc=ryan.roberts@arm.com \
    --cc=tujinjiang@huawei.com \
    --cc=wangkefeng.wang@huawei.com \
    --cc=zengheng4@huawei.com \
    /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