From: Li Zhong <zhong@linux.vnet.ibm.com>
To: Nishanth Aravamudan <nacc@linux.vnet.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org,
Nathan Fontenot <nfont@linux.vnet.ibm.com>,
paulus@samba.org
Subject: Re: [RFC PATCH v3 1/3] powerpc: Fix warning reported by verify_cpu_node_mapping()
Date: Wed, 08 Oct 2014 12:51:02 +0800 [thread overview]
Message-ID: <1412743862.4479.4.camel@TP420> (raw)
In-Reply-To: <20141007153346.GE9339@linux.vnet.ibm.com>
On 二, 2014-10-07 at 08:33 -0700, Nishanth Aravamudan wrote:
> On 07.10.2014 [17:28:38 +1100], Michael Ellerman wrote:
> > On Fri, 2014-10-03 at 16:26 -0700, Nishanth Aravamudan wrote:
> > > 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.
> >
> > Not really your fault, I hadn't announced my trees existence :)
> >
> > > Do we want these to go back to 3.17-stable, as they fix some annoying splats
> > > during boot (non-fatal afaict, though)?
> >
> > Up to you really, I don't know how often/bad they were. I haven't added CC
> > stable tags to the commits, so if you want them in stable you should send them
> > explicitly.
>
> I think they occur every boot, unconditionally, on pseries. Doesn't
> prevent boot, just really noisy. I think it'd be good to get them into
> -stable.
>
> Li Zhong, can you push them once they get sent upstream?
Ok, I will send these patches to stable mailing list after it is merged.
Thanks, Zhong
>
> Thanks,
> Nish
next prev parent reply other threads:[~2014-10-08 4:51 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
2014-10-07 6:28 ` Michael Ellerman
2014-10-07 15:33 ` Nishanth Aravamudan
2014-10-08 4:51 ` Li Zhong [this message]
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=1412743862.4479.4.camel@TP420 \
--to=zhong@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nacc@linux.vnet.ibm.com \
--cc=nfont@linux.vnet.ibm.com \
--cc=paulus@samba.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).