From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: "Hauke Mehrtens" <hauke@hauke-m.de>,
"Rafał Miłecki" <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
Date: Thu, 15 Oct 2020 00:07:40 +0200 [thread overview]
Message-ID: <20201014220740.GA5587@alpha.franken.de> (raw)
In-Reply-To: <alpine.LFD.2.21.2010141344200.866917@eddie.linux-mips.org>
On Wed, Oct 14, 2020 at 01:47:06PM +0100, Maciej W. Rozycki wrote:
> 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?
mips-next branch in
git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2020-10-14 22:09 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
2020-10-14 22:07 ` Thomas Bogendoerfer [this message]
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=20201014220740.GA5587@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--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=macro@linux-mips.org \
--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).