From: Nicholas Piggin <npiggin@gmail.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: Nicholas Piggin <npiggin@gmail.com>,
Michael Ellerman <mpe@ellerman.id.au>
Subject: [PATCH 0/3] sreset debugging improvements
Date: Tue, 4 Jul 2017 20:09:06 +1000 [thread overview]
Message-ID: <20170704100909.8738-1-npiggin@gmail.com> (raw)
These are a few independent patches I've accumulated that improve
system reset handling a bit. The first 2 at least should be quite
straight forward and hopefully can be merged for 4.13.
Thanks,
Nick
Nicholas Piggin (3):
powerpc: do not call ppc_md.panic in panic notifier if fadump not used
powerpc/pseries/le: work around a firmware quirk
powerpc: do not send system reset request through the oops path
arch/powerpc/kernel/setup-common.c | 15 +++++++-----
arch/powerpc/kernel/traps.c | 47 ++++++++++++++++++++++++------------
arch/powerpc/platforms/pseries/ras.c | 15 ++++++++++++
3 files changed, 55 insertions(+), 22 deletions(-)
--
2.11.0
next reply other threads:[~2017-07-04 10:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-04 10:09 Nicholas Piggin [this message]
2017-07-04 10:09 ` [PATCH 1/3] powerpc: do not call ppc_md.panic in panic notifier if fadump not used Nicholas Piggin
2017-07-04 16:52 ` Mahesh Jagannath Salgaonkar
2017-07-04 23:42 ` Michael Ellerman
2017-07-05 0:16 ` Nicholas Piggin
2017-07-04 10:09 ` [PATCH 2/3] powerpc/pseries/le: work around a firmware quirk Nicholas Piggin
2017-07-04 10:09 ` [PATCH 3/3] powerpc: do not send system reset request through the oops path Nicholas Piggin
-- strict thread matches above, loose matches on Subject: below --
2017-07-05 3:56 [PATCH 0/3] sreset debugging improvements Nicholas Piggin
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=20170704100909.8738-1-npiggin@gmail.com \
--to=npiggin@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).