From: martin.petersen@oracle.com (Martin K. Petersen)
Subject: [PATCH] qla2xxx: convert nvme Transport error to internal error
Date: Fri, 15 Sep 2017 21:12:47 -0400 [thread overview]
Message-ID: <yq18thftpio.fsf@oracle.com> (raw)
In-Reply-To: <20170916010947.GA16883@lst.de> (hch@lst.de's message of "Sat, 16 Sep 2017 03:09:47 +0200")
Christoph,
> I've already picked this up with the reset of James' series to get rid
> of these errors in lpfc and the nvme code. I can still rebase the
> nvme tree, but it will require the scsi tree to get in first which is
> a little annoying.
That's fine. I'll just drop it.
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2017-09-16 1:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 18:30 [PATCH] qla2xxx: convert nvme Transport error to internal error James Smart
2017-09-14 19:39 ` Madhani, Himanshu
2017-09-16 1:02 ` Martin K. Petersen
2017-09-16 1:09 ` hch
2017-09-16 1:12 ` Martin K. Petersen [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=yq18thftpio.fsf@oracle.com \
--to=martin.petersen@oracle.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