From: Michael Ellerman <mpe@ellerman.id.au>
To: bharata@linux.vnet.ibm.com, linuxppc-dev@lists.ozlabs.org
Cc: david@gibson.dropbear.id.au, nfont@linux.vnet.ibm.com, aik@au1.ibm.com
Subject: Re: [FIX PATCH v2 0/2] Fix powerpc,numa: Fix memory_hotplug_max()
Date: Tue, 14 Jun 2016 15:19:27 +1000 [thread overview]
Message-ID: <1465881567.17785.2.camel@ellerman.id.au> (raw)
In-Reply-To: <20160614044651.GB5916@in.ibm.com>
On Tue, 2016-06-14 at 10:16 +0530, Bharata B Rao wrote:
> On Thu, May 12, 2016 at 07:04:13PM +0530, Bharata B Rao wrote:
> > This patchset fixes memory_hotplug_max() routine to return correct
> > value of maximum hotpluggable address.
> >
> > In this version, whitespace fixes are separated into a different patch.
> >
> > v2: https://www.mail-archive.com/linuxppc-dev@lists.ozlabs.org/msg103342.html
> >
> > Bharata B Rao (2):
> > powerpc,numa: Fix whitespace in hot_add_drconf_memory_max()
> > powerpc,numa: Fix memory_hotplug_max()
> >
> > arch/powerpc/mm/numa.c | 36 ++++++++++++++++++++++++++----------
> > 1 file changed, 26 insertions(+), 10 deletions(-)
>
> Can this fix be considered for inclusion ? Should I be posting this against
> latest git now ?
No that's fine, it still applies cleanly.
Have you tested this on PowerVM ?
Has this always been broken, or did we break it in a particular commit? If the
latter can you tell me which commit.
Should we be sending this to stable?
cheers
next prev parent reply other threads:[~2016-06-14 5:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 13:34 [FIX PATCH v2 0/2] Fix powerpc,numa: Fix memory_hotplug_max() Bharata B Rao
2016-05-12 13:34 ` [FIX PATCH v2 1/2] powerpc, numa: Fix whitespace in hot_add_drconf_memory_max() Bharata B Rao
2016-05-26 0:47 ` [FIX PATCH v2 1/2] powerpc,numa: " David Gibson
2016-06-21 0:40 ` [FIX, v2, 1/2] powerpc, numa: " Michael Ellerman
2016-05-12 13:34 ` [FIX PATCH v2 2/2] powerpc,numa: Fix memory_hotplug_max() Bharata B Rao
2016-05-26 0:50 ` David Gibson
2016-06-21 0:40 ` [FIX,v2,2/2] " Michael Ellerman
2016-06-14 4:46 ` [FIX PATCH v2 0/2] Fix " Bharata B Rao
2016-06-14 5:19 ` Michael Ellerman [this message]
2016-06-14 5:46 ` Bharata B Rao
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=1465881567.17785.2.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=aik@au1.ibm.com \
--cc=bharata@linux.vnet.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nfont@linux.vnet.ibm.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).