From: Michael Ellerman <mpe@ellerman.id.au>
To: Samuel Mendoza-Jonas <sam.mj@au1.ibm.com>, linuxppc-dev@ozlabs.org
Cc: Samuel Mendoza-Jonas <sam.mj@au1.ibm.com>
Subject: Re: [RFC] powerpc/kexec: Wait 1s for secondaries to enter OPAL
Date: Mon, 12 Oct 2015 22:21:24 +1100 (AEDT) [thread overview]
Message-ID: <20151012112124.84A8F1402B9@ozlabs.org> (raw)
In-Reply-To: <1437544469-20028-1-git-send-email-sam.mj@au1.ibm.com>
On Wed, 2015-22-07 at 05:54:29 UTC, Samuel Mendoza-Jonas wrote:
> Always include a timeout when waiting for secondary cpus to enter OPAL
> in the kexec path, rather than only when crashing.
>
> Signed-off-by: Samuel Mendoza-Jonas <sam.mj@au1.ibm.com>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/1b70386c99e997b359735c75
cheers
prev parent reply other threads:[~2015-10-12 11:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 5:54 [RFC PATCH] powerpc/kexec: Wait 1s for secondaries to enter OPAL Samuel Mendoza-Jonas
2015-07-27 5:56 ` Stewart Smith
2015-07-28 6:13 ` Samuel Mendoza-Jonas
2015-07-28 9:58 ` Benjamin Herrenschmidt
2015-07-29 7:24 ` Stewart Smith
2015-10-12 11:21 ` Michael Ellerman [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=20151012112124.84A8F1402B9@ozlabs.org \
--to=mpe@ellerman.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=sam.mj@au1.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).