From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH 0/5] nvme: remove FC transport status values
Date: Thu, 14 Sep 2017 09:55:30 -0700 [thread overview]
Message-ID: <20170914165530.GA7335@infradead.org> (raw)
In-Reply-To: <20170907232729.28763-1-jsmart2021@gmail.com>
Just trying to check in:
I'm tempted to add this and the transport SGL patch into the for 4.14
tree given that it's mostly trivial and a spec compliance fix.
Do you (and Jens) agree with that?
next prev parent reply other threads:[~2017-09-14 16:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 23:27 [PATCH 0/5] nvme: remove FC transport status values James Smart
2017-09-07 23:27 ` [PATCH 1/5] nvme: remove FC transport-specific error values James Smart
2017-09-08 7:24 ` Christoph Hellwig
2017-09-08 15:23 ` James Smart
2017-09-07 23:27 ` [PATCH 2/5] nvme-fc: remove use of FC-specific error codes James Smart
2017-09-07 23:27 ` [PATCH 3/5] nvmet-fc: " James Smart
2017-09-07 23:27 ` [PATCH 4/5] nvmet-fcloop: " James Smart
2017-09-07 23:27 ` [PATCH 5/5] lpfc: " James Smart
2017-09-14 16:55 ` Christoph Hellwig [this message]
2017-09-14 17:25 ` [PATCH 0/5] nvme: remove FC transport status values James Smart
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=20170914165530.GA7335@infradead.org \
--to=hch@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