[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1611489705.hu96tutmbn.astroid@bobo.none>
Date: Sun, 24 Jan 2021 22:04:47 +1000
From: Nicholas Piggin <npiggin@...il.com>
To: Christoph Hellwig <hch@...radead.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Christophe Leroy <christophe.leroy@...roup.eu>,
Ding Tianhong <dingtianhong@...wei.com>,
Jonathan Cameron <Jonathan.Cameron@...wei.com>,
linux-arch@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, linuxppc-dev@...ts.ozlabs.org,
Zefan Li <lizefan@...wei.com>,
Rick Edgecombe <rick.p.edgecombe@...el.com>
Subject: Re: [PATCH v10 04/12] mm/ioremap: rename ioremap_*_range to
vmap_*_range
Excerpts from Christoph Hellwig's message of January 24, 2021 9:36 pm:
> 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?
>
Yes, I moved it in a later patch to make reviewing easier. Rename in
this one then the move patch is cut and paste.
Thanks,
Nick
Powered by blists - more mailing lists