Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Wed, 14 Oct 2020 13:47:06 +0100 (BST)
From:   "Maciej W. Rozycki" <macro@linux-mips.org>
To:     Thomas Bogendoerfer <tsbogend@alpha.franken.de>
cc:     Hauke Mehrtens <hauke@hauke-m.de>,
        =?UTF-8?Q?Rafa=C5=82_Mi=C5=82ecki?= <zajec5@gmail.com>,
        Florian Fainelli <f.fainelli@gmail.com>,
        bcm-kernel-feedback-list@broadcom.com,
        Jiaxun Yang <jiaxun.yang@flygoat.com>,
        Keguang Zhang <keguang.zhang@gmail.com>,
        John Crispin <john@phrozen.org>, linux-mips@vger.kernel.org,
        linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3] MIPS: replace add_memory_region with memblock
In-Reply-To: <20201009121449.64081-1-tsbogend@alpha.franken.de>
Message-ID: <alpine.LFD.2.21.2010141344200.866917@eddie.linux-mips.org>
References: <20201009121449.64081-1-tsbogend@alpha.franken.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Precedence: bulk

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@alpha.franken.de>

 For the DEC part:

Acked-by: Maciej W. Rozycki <macro@linux-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