From: sathya.m@samsung.com (Sathyavathi M)
Subject: Fwd: Fwd: Fwd: Re: Fwd: Fwd: Re: PCIe error handling patch
Date: Wed, 16 Sep 2015 10:03:35 +0000 (GMT) [thread overview]
Message-ID: <1107870359.1155791442397814537.JavaMail.weblogic@ep2mlwas06d> (raw)
Hi Keith,
Can you merge the below patch to latest kernels.
http://lists.infradead.org/pipermail/linux-nvme/2015-June/001949.html
Regards,
Sathya
------- Original Message -------
Sender : Keith Busch
Date : Jun 12, 2015 23:06 (GMT+09:00)
Title : Re: Fwd: Fwd: Re: PCIe error handling patch
On Fri, 12 Jun 2015, Sathyavathi M wrote:
> I was able to test the PCIe error handling patch on IBM power pc machine.
> The patch works for me without the delay mention in the NVMe: PCI error handling code patch.
> If an EEH is triggered the system recovers and resume back any ios.
> So I would request you to pull the EEH patch without the delay.
Hi Sathya,
You're saying the same AER patch, plus removing the msleep, tests
successfully with EEH h/w? If so, that's great! I'll have it merged up
to the latest kernel to test on other platforms, then we can resubmit
the patch.
Thanks,
Keith
reply other threads:[~2015-09-16 10:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1107870359.1155791442397814537.JavaMail.weblogic@ep2mlwas06d \
--to=sathya.m@samsung.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).