[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180905172017.GA2203@rapoport-lnx>
Date: Wed, 5 Sep 2018 20:20:18 +0300
From: Mike Rapoport <rppt@...ux.vnet.ibm.com>
To: Rob Herring <robh@...nel.org>
Cc: linux-mm@...ck.org, Andrew Morton <akpm@...ux-foundation.org>,
davem@...emloft.net,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
mingo@...hat.com, Michael Ellerman <mpe@...erman.id.au>,
mhocko@...e.com, paul.burton@...s.com,
Thomas Gleixner <tglx@...utronix.de>, tony.luck@...el.com,
linux-ia64@...r.kernel.org, linux-mips@...ux-mips.org,
linuxppc-dev@...ts.ozlabs.org, sparclinux@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH 07/29] memblock: remove _virt from APIs returning
virtual address
On Wed, Sep 05, 2018 at 12:04:36PM -0500, Rob Herring wrote:
> On Wed, Sep 5, 2018 at 11:00 AM Mike Rapoport <rppt@...ux.vnet.ibm.com> wrote:
> >
> > The conversion is done using
> >
> > sed -i 's@...block_virt_alloc@...block_alloc@g' \
> > $(git grep -l memblock_virt_alloc)
>
> What's the reason to do this? It seems like a lot of churn even if a
> mechanical change.
I felt that memblock_virt_alloc_ is too long for a prefix, e.g:
memblock_virt_alloc_node_nopanic, memblock_virt_alloc_low_nopanic.
And for consistency I've changed the memblock_virt_alloc as well.
> Rob
>
--
Sincerely yours,
Mike.
Powered by blists - more mailing lists