From: Nicholas Piggin <npiggin@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
mhocko@suse.com, catalin.marinas@arm.com,
pasha.tatashin@oracle.com, takahiro.akashi@linaro.org,
gi-oh.kim@profitbricks.com, baiyaowei@cmss.chinamobile.com,
bob.picco@oracle.com, ard.biesheuvel@linaro.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: OK to merge via powerpc? (was Re: [PATCH 05/14] mm: make memblock_alloc_base_nid non-static)
Date: Wed, 14 Mar 2018 10:56:20 +1000 [thread overview]
Message-ID: <20180314105620.5d98ff9f@roar.ozlabs.ibm.com> (raw)
In-Reply-To: <20180313124128.875efd39a5d3ce9a9bb37e63@linux-foundation.org>
On Tue, 13 Mar 2018 12:41:28 -0700
Andrew Morton <akpm@linux-foundation.org> wrote:
> On Tue, 13 Mar 2018 23:06:35 +1100 Michael Ellerman <mpe@ellerman.id.au> wrote:
>
> > Anyone object to us merging the following patch via the powerpc tree?
> >
> > Full series is here if anyone's interested:
> > http://patchwork.ozlabs.org/project/linuxppc-dev/list/?series=28377&state=*
> >
>
> Yup, please go ahead.
>
> I assume the change to the memblock_alloc_range() declaration was an
> unrelated, unchangelogged cleanup.
>
It is. I'm trying to get better at that. Michael might drop that bit if
he's not already sick of fixing up my patches...
Thanks,
Nick
prev parent reply other threads:[~2018-03-14 0:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180213150824.27689-1-npiggin@gmail.com>
[not found] ` <20180213150824.27689-6-npiggin@gmail.com>
2018-03-13 12:06 ` OK to merge via powerpc? (was Re: [PATCH 05/14] mm: make memblock_alloc_base_nid non-static) Michael Ellerman
2018-03-13 19:41 ` Andrew Morton
2018-03-14 0:56 ` Nicholas Piggin [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=20180314105620.5d98ff9f@roar.ozlabs.ibm.com \
--to=npiggin@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=ard.biesheuvel@linaro.org \
--cc=baiyaowei@cmss.chinamobile.com \
--cc=bob.picco@oracle.com \
--cc=catalin.marinas@arm.com \
--cc=gi-oh.kim@profitbricks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mhocko@suse.com \
--cc=mpe@ellerman.id.au \
--cc=pasha.tatashin@oracle.com \
--cc=takahiro.akashi@linaro.org \
/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).