From: keith.busch@intel.com (Keith Busch)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 00/12] error handling and pciehp maintenance
Date: Tue, 6 Nov 2018 10:26:08 -0700 [thread overview]
Message-ID: <20181106172608.GB6217@localhost.localdomain> (raw)
In-Reply-To: <20181106172100.GA22063@e107981-ln.cambridge.arm.com>
On Tue, Nov 06, 2018 at 05:21:00PM +0000, Lorenzo Pieralisi wrote:
> If you have a simple reproducer for the bugs I am happy to help you test
> it (I can also apply arm64 DYNAMIC_FTRACE_WITH_REGS patches and test that
> new code path if that's the final direction we are taking).
The easiest way to reproduce is load the aer_inject module, inject an
error into a bridge, then remove the bridge and rescan.
next prev parent reply other threads:[~2018-11-06 17:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180918235848.26694-1-keith.busch@intel.com>
[not found] ` <20181004214015.GK120535@bhelgaas-glaptop.roam.corp.google.com>
[not found] ` <20181004221137.GB21834@localhost.localdomain>
2018-10-05 17:31 ` [PATCH 00/12] error handling and pciehp maintenance Bjorn Helgaas
2018-10-08 16:18 ` Keith Busch
2018-10-08 17:23 ` Bjorn Helgaas
2018-11-06 16:34 ` Lorenzo Pieralisi
2018-11-06 16:47 ` Keith Busch
2018-11-06 17:21 ` Lorenzo Pieralisi
2018-11-06 17:26 ` Keith Busch [this message]
2018-10-09 16:03 ` Will Deacon
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=20181106172608.GB6217@localhost.localdomain \
--to=keith.busch@intel.com \
--cc=linux-arm-kernel@lists.infradead.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