[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190211110613.GC30880@fuggles.cambridge.arm.com>
Date: Mon, 11 Feb 2019 11:06:13 +0000
From: Will Deacon <will.deacon@....com>
To: Peng Fan <peng.fan@....com>
Cc: "catalin.marinas@....com" <catalin.marinas@....com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"rppt@...ux.vnet.ibm.com" <rppt@...ux.vnet.ibm.com>,
"ard.biesheuvel@...aro.org" <ard.biesheuvel@...aro.org>,
"f.fainelli@...il.com" <f.fainelli@...il.com>,
"robin.murphy@....com" <robin.murphy@....com>,
"james.morse@....com" <james.morse@....com>,
"ghackmann@...roid.com" <ghackmann@...roid.com>,
"stefan@...er.ch" <stefan@...er.ch>,
"hannes@...xchg.org" <hannes@...xchg.org>,
"logang@...tatee.com" <logang@...tatee.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"van.freenix@...il.com" <van.freenix@...il.com>
Subject: Re: [PATCH] arm64: use memblocks_present
On Sun, Feb 10, 2019 at 09:28:43AM +0000, Peng Fan wrote:
> arm64_memory_present is doing same thing as memblocks_present, so
> let's use common code memblocks_present instead of platform
> specific arm64_memory_present.
>
> Signed-off-by: Peng Fan <peng.fan@....com>
> ---
> arch/arm64/mm/init.c | 20 +-------------------
> 1 file changed, 1 insertion(+), 19 deletions(-)
Acked-by: Will Deacon <will.deacon@....com>
Catalin -- can you pick this one up, please?
Will
Powered by blists - more mailing lists