[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <d21d10ab-ce32-9f4c-205a-43ad02c11300@deltatee.com>
Date: Mon, 11 Feb 2019 10:26:11 -0700
From: Logan Gunthorpe <logang@...tatee.com>
To: Peng Fan <peng.fan@....com>,
"catalin.marinas@....com" <catalin.marinas@....com>,
"will.deacon@....com" <will.deacon@....com>
Cc: "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>,
"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 2019-02-10 2:28 a.m., 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.
I've already sent patches for this[1]. The arm64 one was already queued
up by Catalin.
Thanks,
Logan
Powered by blists - more mailing lists