From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: "Florian Fainelli" <f.fainelli@gmail.com>,
"Hauke Mehrtens" <hauke@hauke-m.de>,
"Rafał Miłecki" <zajec5@gmail.com>,
linux-mips@vger.kernel.org,
"Jiaxun Yang" <jiaxun.yang@flygoat.com>,
linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
"John Crispin" <john@phrozen.org>,
"Keguang Zhang" <keguang.zhang@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3] MIPS: replace add_memory_region with memblock
Date: Wed, 14 Oct 2020 13:47:06 +0100 (BST) [thread overview]
Message-ID: <alpine.LFD.2.21.2010141344200.866917@eddie.linux-mips.org> (raw)
In-Reply-To: <20201009121449.64081-1-tsbogend@alpha.franken.de>
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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-10-14 12:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 12:14 [PATCH v3] MIPS: replace add_memory_region with memblock Thomas Bogendoerfer
2020-10-12 10:31 ` Thomas Bogendoerfer
2020-10-14 12:47 ` Maciej W. Rozycki [this message]
2020-10-14 22:07 ` Thomas Bogendoerfer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.21.2010141344200.866917@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=hauke@hauke-m.de \
--cc=jiaxun.yang@flygoat.com \
--cc=john@phrozen.org \
--cc=keguang.zhang@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=tsbogend@alpha.franken.de \
--cc=zajec5@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).