All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org, Zefan Li <lizefan@huawei.com>,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	Christoph Hellwig <hch@infradead.org>,
	Christophe Leroy <christophe.leroy@csgroup.eu>,
	Rick Edgecombe <rick.p.edgecombe@intel.com>,
	Ding Tianhong <dingtianhong@huawei.com>
Subject: Re: [PATCH v10 04/12] mm/ioremap: rename ioremap_*_range to vmap_*_range
Date: Sun, 24 Jan 2021 11:36:36 +0000	[thread overview]
Message-ID: <20210124113636.GD694255@infradead.org> (raw)
In-Reply-To: <20210124082230.2118861-5-npiggin@gmail.com>

On Sun, Jan 24, 2021 at 06:22:22PM +1000, Nicholas Piggin wrote:
> This will be used as a generic kernel virtual mapping function, so
> re-name it in preparation.

The new name looks ok, but shouldn't it also move to vmalloc.c with
the more generic name and purpose?

WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: linux-arch@vger.kernel.org,
	Ding Tianhong <dingtianhong@huawei.com>,
	linux-kernel@vger.kernel.org,
	Christoph Hellwig <hch@infradead.org>,
	linux-mm@kvack.org, Zefan Li <lizefan@huawei.com>,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Rick Edgecombe <rick.p.edgecombe@intel.com>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v10 04/12] mm/ioremap: rename ioremap_*_range to vmap_*_range
Date: Sun, 24 Jan 2021 11:36:36 +0000	[thread overview]
Message-ID: <20210124113636.GD694255@infradead.org> (raw)
In-Reply-To: <20210124082230.2118861-5-npiggin@gmail.com>

On Sun, Jan 24, 2021 at 06:22:22PM +1000, Nicholas Piggin wrote:
> This will be used as a generic kernel virtual mapping function, so
> re-name it in preparation.

The new name looks ok, but shouldn't it also move to vmalloc.c with
the more generic name and purpose?

  reply	other threads:[~2021-01-24 11:38 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-24  8:22 [PATCH v10 00/12] huge vmalloc mappings Nicholas Piggin
2021-01-24  8:22 ` Nicholas Piggin
2021-01-24  8:22 ` [PATCH v10 01/12] mm/vmalloc: fix vmalloc_to_page for huge vmap mappings Nicholas Piggin
2021-01-24  8:22   ` Nicholas Piggin
2021-01-24 11:31   ` Christoph Hellwig
2021-01-24 11:31     ` Christoph Hellwig
2021-01-24  8:22 ` [PATCH v10 02/12] mm: apply_to_pte_range warn and fail if a large pte is encountered Nicholas Piggin
2021-01-24  8:22   ` Nicholas Piggin
2021-01-24 11:32   ` Christoph Hellwig
2021-01-24 11:32     ` Christoph Hellwig
2021-01-24  8:22 ` [PATCH v10 03/12] mm/vmalloc: rename vmap_*_range vmap_pages_*_range Nicholas Piggin
2021-01-24  8:22   ` Nicholas Piggin
2021-01-24 11:34   ` Christoph Hellwig
2021-01-24 11:34     ` Christoph Hellwig
2021-01-24  8:22 ` [PATCH v10 04/12] mm/ioremap: rename ioremap_*_range to vmap_*_range Nicholas Piggin
2021-01-24  8:22   ` Nicholas Piggin
2021-01-24 11:36   ` Christoph Hellwig [this message]
2021-01-24 11:36     ` Christoph Hellwig
2021-01-24 12:04     ` Nicholas Piggin
2021-01-24 12:04       ` Nicholas Piggin
2021-01-24  8:22 ` [PATCH v10 05/12] mm: HUGE_VMAP arch support cleanup Nicholas Piggin
2021-01-24  8:22   ` Nicholas Piggin
2021-01-24  8:22   ` Nicholas Piggin
2021-01-24 11:40   ` Christoph Hellwig
2021-01-24 11:40     ` Christoph Hellwig
2021-01-24 11:40     ` Christoph Hellwig
2021-01-24 12:22     ` Nicholas Piggin
2021-01-24 12:22       ` Nicholas Piggin
2021-01-24 12:22       ` Nicholas Piggin
2021-01-25  8:19     ` Christophe Leroy
2021-01-25  8:19       ` Christophe Leroy
2021-01-25  8:19       ` Christophe Leroy
2021-01-25  8:40   ` Christophe Leroy
2021-01-25  8:40     ` Christophe Leroy
2021-01-25  8:40     ` Christophe Leroy
2021-01-24  8:22 ` [PATCH v10 06/12] powerpc: inline huge vmap supported functions Nicholas Piggin
2021-01-24  8:22   ` Nicholas Piggin
2021-01-25  8:42   ` Christophe Leroy
2021-01-25  8:42     ` Christophe Leroy
2021-01-25 11:37     ` Nicholas Piggin
2021-01-25 11:37       ` Nicholas Piggin
2021-01-24  8:22 ` [PATCH v10 07/12] arm64: " Nicholas Piggin
2021-01-24  8:22   ` Nicholas Piggin
2021-01-24  8:22   ` Nicholas Piggin
2021-01-24  8:22 ` [PATCH v10 08/12] x86: " Nicholas Piggin
2021-01-24  8:22   ` Nicholas Piggin
2021-01-24  8:22 ` [PATCH v10 09/12] mm: Move vmap_range from mm/ioremap.c to mm/vmalloc.c Nicholas Piggin
2021-01-24  8:22   ` Nicholas Piggin
2021-01-24 14:49   ` Christoph Hellwig
2021-01-24 14:49     ` Christoph Hellwig
2021-01-24  8:22 ` [PATCH v10 10/12] mm/vmalloc: add vmap_range_noflush variant Nicholas Piggin
2021-01-24  8:22   ` Nicholas Piggin
2021-01-24 14:51   ` Christoph Hellwig
2021-01-24 14:51     ` Christoph Hellwig
2021-01-24  8:22 ` [PATCH v10 11/12] mm/vmalloc: Hugepage vmalloc mappings Nicholas Piggin
2021-01-24  8:22   ` Nicholas Piggin
2021-01-24 15:07   ` Christoph Hellwig
2021-01-24 15:07     ` Christoph Hellwig
2021-01-24 18:06     ` Randy Dunlap
2021-01-24 18:06       ` Randy Dunlap
2021-01-24 23:17     ` Nicholas Piggin
2021-01-24 23:17       ` Nicholas Piggin
2021-01-25  9:14   ` Christophe Leroy
2021-01-25  9:14     ` Christophe Leroy
2021-01-25 11:37     ` Nicholas Piggin
2021-01-25 11:37       ` Nicholas Piggin
2021-01-25 12:13       ` Christophe Leroy
2021-01-25 12:13         ` Christophe Leroy
2021-01-25 12:24     ` David Laight
2021-01-26  9:50       ` Nicholas Piggin
2021-01-26  9:50         ` Nicholas Piggin
2021-01-24  8:22 ` [PATCH v10 12/12] powerpc/64s/radix: Enable huge " Nicholas Piggin
2021-01-24  8:22   ` Nicholas Piggin

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=20210124113636.GD694255@infradead.org \
    --to=hch@infradead.org \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=christophe.leroy@csgroup.eu \
    --cc=dingtianhong@huawei.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=lizefan@huawei.com \
    --cc=npiggin@gmail.com \
    --cc=rick.p.edgecombe@intel.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 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.