[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.21.2010141344200.866917@eddie.linux-mips.org>
Date: Wed, 14 Oct 2020 13:47:06 +0100 (BST)
From: "Maciej W. Rozycki" <macro@...ux-mips.org>
To: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
cc: Hauke Mehrtens <hauke@...ke-m.de>,
Rafał Miłecki <zajec5@...il.com>,
Florian Fainelli <f.fainelli@...il.com>,
bcm-kernel-feedback-list@...adcom.com,
Jiaxun Yang <jiaxun.yang@...goat.com>,
Keguang Zhang <keguang.zhang@...il.com>,
John Crispin <john@...ozen.org>, linux-mips@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v3] MIPS: replace add_memory_region with memblock
On Fri, 9 Oct 2020, Thomas Bogendoerfer wrote:
> add_memory_region was the old interface for registering memory and
> was already changed to used memblock internaly. Replace it by
> directly calling memblock functions.
>
> Signed-off-by: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
For the DEC part:
Acked-by: Maciej W. Rozycki <macro@...ux-mips.org>
NB this does not apply cleanly to upstream master, but I was able to
verify this regardless as the DEC part does. For future reference: what
tree do you usually use that you post patches against?
Maciej
Powered by blists - more mailing lists