linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Nicholas Piggin <npiggin@gmail.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: Nicholas Piggin <npiggin@gmail.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Mahesh Jagannath Salgaonkar <mahesh@linux.vnet.ibm.com>
Subject: [PATCH 0/3] sreset debugging improvements
Date: Wed,  5 Jul 2017 13:56:24 +1000	[thread overview]
Message-ID: <20170705035627.19563-1-npiggin@gmail.com> (raw)

Since last time:
- Fixed bug in the fadump patch noticed by Mahesh.
- Removed ppc_md.panic completely.

Nicholas Piggin (3):
  powerpc: do not call ppc_md.panic in fadump panic notifier
  powerpc/pseries/le: work around a firmware quirk
  powerpc: do not send system reset request through the oops path

 arch/powerpc/include/asm/machdep.h     |  1 -
 arch/powerpc/include/asm/setup.h       |  1 -
 arch/powerpc/kernel/fadump.c           | 22 ++++++++++++++++
 arch/powerpc/kernel/setup-common.c     | 27 -------------------
 arch/powerpc/kernel/traps.c            | 47 ++++++++++++++++++++++------------
 arch/powerpc/platforms/ps3/setup.c     | 15 -----------
 arch/powerpc/platforms/pseries/ras.c   | 15 +++++++++++
 arch/powerpc/platforms/pseries/setup.c |  1 -
 8 files changed, 68 insertions(+), 61 deletions(-)

-- 
2.11.0

             reply	other threads:[~2017-07-05  3:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-05  3:56 Nicholas Piggin [this message]
2017-07-05  3:56 ` [PATCH v2 1/3] powerpc: do not call ppc_md.panic in fadump panic notifier Nicholas Piggin
2017-07-05  4:11   ` Mahesh Jagannath Salgaonkar
2017-08-31 11:36   ` [v2, " Michael Ellerman
2017-07-05  3:56 ` [PATCH v2 2/3] powerpc/pseries/le: work around a firmware quirk Nicholas Piggin
2017-07-05  3:56 ` [PATCH v2 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-04 10:09 [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=20170705035627.19563-1-npiggin@gmail.com \
    --to=npiggin@gmail.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mahesh@linux.vnet.ibm.com \
    --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).