Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: hch@lst.de (hch@lst.de)
Subject: [PATCH] qla2xxx: convert nvme Transport error to internal error
Date: Sat, 16 Sep 2017 03:09:47 +0200	[thread overview]
Message-ID: <20170916010947.GA16883@lst.de> (raw)
In-Reply-To: <yq1poartq01.fsf@oracle.com>

On Fri, Sep 15, 2017@09:02:22PM -0400, Martin K. Petersen wrote:
> 
> Himanshu,
> 
> >> Patch removing transport-specific errors crosssed with a qla2xxx update
> >> that referenced the status value being removed.
> >> 
> >> Swap status to an internal error.
> 
> Applied to 4.14/scsi-fixes.

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.

  reply	other threads:[~2017-09-16  1:09 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 [this message]
2017-09-16  1:12       ` Martin K. Petersen

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=20170916010947.GA16883@lst.de \
    --to=hch@lst.de \
    /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