All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Aravamudan <nacc@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: paulus@samba.org, linuxppc-dev@lists.ozlabs.org,
	Li Zhong <zhong@linux.vnet.ibm.com>,
	Nathan Fontenot <nfont@linux.vnet.ibm.com>
Subject: Re: [RFC PATCH v3 1/3] powerpc: Fix warning reported by verify_cpu_node_mapping()
Date: Fri, 3 Oct 2014 16:26:06 -0700	[thread overview]
Message-ID: <20141003232606.GA9339@linux.vnet.ibm.com> (raw)
In-Reply-To: <1412297420.2783.3.camel@concordia>

On 03.10.2014 [10:50:20 +1000], Michael Ellerman wrote:
> On Thu, 2014-10-02 at 14:13 -0700, Nishanth Aravamudan wrote:
> > Ben & Michael,
> > 
> > What's the status of these patches?
> 
> Been in my next for a week :)
> 
> https://git.kernel.org/cgit/linux/kernel/git/mpe/linux.git/log/?h=next

Ah ok, thanks -- I wasn't following your tree, my fault. Do we want
these to go back to 3.17-stable, as they fix some annoying splats during
boot (non-fatal afaict, though)?

-Nish

  reply	other threads:[~2014-10-03 23:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-27  9:33 [RFC PATCH v3 1/3] powerpc: Fix warning reported by verify_cpu_node_mapping() Li Zhong
2014-08-27  9:34 ` [RFC PATCH v3 2/3] powerpc: Only set numa node information for present cpus at boottime Li Zhong
2014-09-03  3:02   ` Nishanth Aravamudan
2014-09-04  3:53     ` Cyril Bur
2014-08-27  9:34 ` [RFC PATCH v3 3/3] powerpc: some changes in numa_setup_cpu() Li Zhong
2014-09-03  3:04   ` Nishanth Aravamudan
2014-09-03  3:01 ` [RFC PATCH v3 1/3] powerpc: Fix warning reported by verify_cpu_node_mapping() Nishanth Aravamudan
2014-10-02 21:13 ` Nishanth Aravamudan
2014-10-02 21:28   ` Benjamin Herrenschmidt
2014-10-02 21:53     ` Nishanth Aravamudan
2014-10-02 22:23       ` Benjamin Herrenschmidt
2014-10-03  0:50   ` Michael Ellerman
2014-10-03 23:26     ` Nishanth Aravamudan [this message]
2014-10-07  6:28       ` Michael Ellerman
2014-10-07 15:33         ` Nishanth Aravamudan
2014-10-08  4:51           ` Li Zhong
2014-10-14  2:39           ` Li Zhong
2014-10-14  4:35             ` Michael Ellerman
2014-10-15  7:34               ` Li Zhong

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=20141003232606.GA9339@linux.vnet.ibm.com \
    --to=nacc@linux.vnet.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=nfont@linux.vnet.ibm.com \
    --cc=paulus@samba.org \
    --cc=zhong@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.