linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Guilherme G. Piccoli" <gpiccoli@linux.vnet.ibm.com>
To: Liu ping fan <kernelfans@gmail.com>, linuxppc-dev@lists.ozlabs.org
Cc: Thadeu Lima de Souza Cascardo <cascardo@canonical.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	paulus <paulus@samba.org>
Subject: Re: what is the state about "[v2] ppc64 boot: Wait for boot cpu to show up if nr_cpus limit is about to hit"
Date: Wed, 6 Dec 2017 14:24:50 -0200	[thread overview]
Message-ID: <8c3d1f7d-f79b-8237-1a1c-97847a77804e@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAFgQCTvOGfq2b861rgosCWD3EMNUOd-vVUp2K_sQYcWqeVepcQ@mail.gmail.com>



On 11/28/2017 04:03 AM, Liu ping fan wrote:
> Hi,
> 
> I can not find the history about:
> https://patchwork.ozlabs.org/patch/577193/
> 
> 
> Can we have this patch?
> 
> Thanks,
> Pingfan
> 

Cross-referencing 2 threads on the same topic:
https://patchwork.ozlabs.org/patch/834860

Cascardo recently rebased this patch against latest kernel and tried to
get v3 merged, on the above linked thread.

Let's choose one of the threads to further discuss the solution to this
long-term bug!

Thanks,


Guilherme

      parent reply	other threads:[~2017-12-06 16:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-28  6:03 what is the state about "[v2] ppc64 boot: Wait for boot cpu to show up if nr_cpus limit is about to hit" Liu ping fan
2017-11-28 11:05 ` Michael Ellerman
2017-12-06 16:24 ` Guilherme G. Piccoli [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=8c3d1f7d-f79b-8237-1a1c-97847a77804e@linux.vnet.ibm.com \
    --to=gpiccoli@linux.vnet.ibm.com \
    --cc=benh@kernel.crashing.org \
    --cc=cascardo@canonical.com \
    --cc=kernelfans@gmail.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --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).