linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Guilherme G. Piccoli" <gpiccoli@linux.vnet.ibm.com>
To: Thadeu Lima de Souza Cascardo <cascardo@canonical.com>,
	linuxppc-dev@lists.ozlabs.org
Cc: mahesh@linux.vnet.ibm.com, npiggin@gmail.com,
	Michael Ellerman <mpe@ellerman.id.au>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	paulus <paulus@samba.org>, Liu ping fan <kernelfans@gmail.com>
Subject: Re: [PATCH v3] ppc64 boot: Wait for boot cpu to show up if nr_cpus limit is about to hit.
Date: Wed, 6 Dec 2017 14:28:24 -0200	[thread overview]
Message-ID: <02a3f733-567d-8c99-abca-82066e08d980@linux.vnet.ibm.com> (raw)
In-Reply-To: <20171129124035.qp3sdmfprcbwh2sn@calabresa>

On 11/29/2017 10:40 AM, Thadeu Lima de Souza Cascardo wrote:
> Ping. Any further reviews/comments? Or any chance of this getting
> applied soon?
> 
> Thanks.
> Cascardo.
> 


Cross-referencing 2 threads on the same topic:
https://lists.ozlabs.org/pipermail/linuxppc-dev/2017-November/166328.html


Liu ping fan asked the state of this patch in the above link of mailing
list thread.
Let's choose one of the threads to further discuss the solution to this
long-term bug!

Thanks,


Guilherme

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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-06 17:34 [PATCH v3] ppc64 boot: Wait for boot cpu to show up if nr_cpus limit is about to hit Thadeu Lima de Souza Cascardo
2017-11-16 21:26 ` Guilherme G. Piccoli
2017-11-17 17:26   ` Thadeu Lima de Souza Cascardo
2017-11-17 17:57     ` Guilherme G. Piccoli
2017-11-29 12:40 ` Thadeu Lima de Souza Cascardo
2017-12-06 16:28   ` 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=02a3f733-567d-8c99-abca-82066e08d980@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=mahesh@linux.vnet.ibm.com \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.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).