All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Kefeng Wang <wangkefeng.wang@huawei.com>,
	catalin.marinas@arm.com, will@kernel.org,
	akpm@linux-foundation.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, hch@infradead.org, arnd@arndb.de,
	Russell King <linux@armlinux.org.uk>
Subject: Re: [PATCH v3 1/6] ARM: mm: kill unused runtime hook arch_iounmap()
Date: Thu, 19 May 2022 14:21:35 +0530	[thread overview]
Message-ID: <28f76e4d-7feb-5811-5130-7b038dcea098@arm.com> (raw)
In-Reply-To: <20220519082552.117736-2-wangkefeng.wang@huawei.com>



On 5/19/22 13:55, Kefeng Wang wrote:
> Since the following commits,
> 
> v5.4
>   commit 59d3ae9a5bf6 ("ARM: remove Intel iop33x and iop13xx support")
> v5.11
>   commit 3e3f354bc383 ("ARM: remove ebsa110 platform")
> 
> The runtime hook arch_iounmap() on ARM is useless, kill arch_iounmap()
> and __iounmap(), and the naming of arch_iounmap will be used in 
> GENERIC_IOREMAP with the later patch.
> 
> Cc: Russell King <linux@armlinux.org.uk>
> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>

LGTM, also builds on multiple arm configs but will let Russel take a look.

WARNING: multiple messages have this Message-ID (diff)
From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Kefeng Wang <wangkefeng.wang@huawei.com>,
	catalin.marinas@arm.com, will@kernel.org,
	akpm@linux-foundation.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, hch@infradead.org, arnd@arndb.de,
	Russell King <linux@armlinux.org.uk>
Subject: Re: [PATCH v3 1/6] ARM: mm: kill unused runtime hook arch_iounmap()
Date: Thu, 19 May 2022 14:21:35 +0530	[thread overview]
Message-ID: <28f76e4d-7feb-5811-5130-7b038dcea098@arm.com> (raw)
In-Reply-To: <20220519082552.117736-2-wangkefeng.wang@huawei.com>



On 5/19/22 13:55, Kefeng Wang wrote:
> Since the following commits,
> 
> v5.4
>   commit 59d3ae9a5bf6 ("ARM: remove Intel iop33x and iop13xx support")
> v5.11
>   commit 3e3f354bc383 ("ARM: remove ebsa110 platform")
> 
> The runtime hook arch_iounmap() on ARM is useless, kill arch_iounmap()
> and __iounmap(), and the naming of arch_iounmap will be used in 
> GENERIC_IOREMAP with the later patch.
> 
> Cc: Russell King <linux@armlinux.org.uk>
> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>

LGTM, also builds on multiple arm configs but will let Russel take a look.

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

  reply	other threads:[~2022-05-19  8:51 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-19  8:25 [PATCH v3 0/6] arm64: Cleanup ioremap() and support ioremap_prot() Kefeng Wang
2022-05-19  8:25 ` Kefeng Wang
2022-05-19  8:25 ` [PATCH v3 1/6] ARM: mm: kill unused runtime hook arch_iounmap() Kefeng Wang
2022-05-19  8:25   ` Kefeng Wang
2022-05-19  8:51   ` Anshuman Khandual [this message]
2022-05-19  8:51     ` Anshuman Khandual
2022-05-20 15:28   ` Catalin Marinas
2022-05-20 15:28     ` Catalin Marinas
2022-05-24  2:03     ` Kefeng Wang
2022-05-24  2:03       ` Kefeng Wang
2022-05-21 20:30   ` Arnd Bergmann
2022-05-21 20:30     ` Arnd Bergmann
2022-05-19  8:25 ` [PATCH v3 2/6] mm: ioremap: Use more sensibly name in ioremap_prot() Kefeng Wang
2022-05-19  8:25   ` Kefeng Wang
2022-05-19  8:25 ` [PATCH v3 3/6] mm: ioremap: Setup phys_addr of struct vm_struct Kefeng Wang
2022-05-19  8:25   ` Kefeng Wang
2022-05-19  8:25 ` [PATCH v3 4/6] mm: ioremap: Add arch_ioremap/iounmap() Kefeng Wang
2022-05-19  8:25   ` Kefeng Wang
2022-05-19 18:52   ` Andrew Morton
2022-05-19 18:52     ` Andrew Morton
2022-05-20  1:22     ` Kefeng Wang
2022-05-20  1:22       ` Kefeng Wang
2022-05-23  3:57     ` Anshuman Khandual
2022-05-23  3:57       ` Anshuman Khandual
2022-05-23 22:17   ` kernel test robot
2022-05-23 22:17     ` kernel test robot
2022-05-24  9:48     ` Kefeng Wang
2022-05-24  9:48       ` Kefeng Wang
2022-05-24  9:48       ` Kefeng Wang
2022-05-24 12:35       ` Arnd Bergmann
2022-05-24 12:35         ` Arnd Bergmann
2022-05-24 12:35         ` Arnd Bergmann
2022-05-24 14:31         ` Kefeng Wang
2022-05-24 14:31           ` Kefeng Wang
2022-05-24 14:31           ` Kefeng Wang
2022-05-24 12:37   ` Arnd Bergmann
2022-05-24 12:37     ` Arnd Bergmann
2022-05-24 14:32     ` Kefeng Wang
2022-05-24 14:32       ` Kefeng Wang
2022-05-24 14:47       ` Arnd Bergmann
2022-05-24 14:47         ` Arnd Bergmann
2022-05-24 14:53         ` Kefeng Wang
2022-05-24 14:53           ` Kefeng Wang
2022-05-31  6:13           ` Christoph Hellwig
2022-05-31  6:13             ` Christoph Hellwig
2022-06-01  1:05             ` Kefeng Wang
2022-06-01  1:05               ` Kefeng Wang
2022-05-19  8:25 ` [PATCH v3 5/6] arm64: mm: Convert to GENERIC_IOREMAP Kefeng Wang
2022-05-19  8:25   ` Kefeng Wang
2022-05-19  8:25 ` [PATCH v3 6/6] arm64: Add HAVE_IOREMAP_PROT support Kefeng Wang
2022-05-19  8:25   ` Kefeng Wang

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=28f76e4d-7feb-5811-5130-7b038dcea098@arm.com \
    --to=anshuman.khandual@arm.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=hch@infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux@armlinux.org.uk \
    --cc=wangkefeng.wang@huawei.com \
    --cc=will@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.