From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH v2 4/5] nvmet_fc: Rework target side abort handling
Date: Wed, 19 Apr 2017 12:36:25 -0700 [thread overview]
Message-ID: <20170419193625.GE18191@infradead.org> (raw)
In-Reply-To: <20170411183232.8955-5-jsmart2021@gmail.com>
This looks ok as a change to the existing code:
Reviewed-by: Christoph Hellwig <hch at lst.de>
But we really need to go to the NVMe technical working group about
how to cater for the fact that the FC transport does transport aborts
(and thus probably doesn't use NVMe aborts at all, although we'd need
to clarify that). Can you reach out to the working group and the T11
folks?
next prev parent reply other threads:[~2017-04-19 19:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 18:32 [PATCH v2 0/5] nvmet_fc: bug fixes and lldd api mods jsmart2021
2017-04-11 18:32 ` [PATCH v2 1/5] nvmet_fc: add target feature flags for upcall isr contexts jsmart2021
2017-04-19 19:33 ` Christoph Hellwig
2017-04-11 18:32 ` [PATCH v2 2/5] nvmet_fc: add req_release to lldd api jsmart2021
2017-04-19 19:34 ` Christoph Hellwig
2017-04-11 18:32 ` [PATCH v2 3/5] nvme_fcloop: split job struct from transport for req_release jsmart2021
2017-04-19 19:34 ` Christoph Hellwig
2017-04-11 18:32 ` [PATCH v2 4/5] nvmet_fc: Rework target side abort handling jsmart2021
2017-04-19 19:36 ` Christoph Hellwig [this message]
2017-04-19 23:19 ` James Smart
2017-04-11 18:32 ` [PATCH v2 5/5] nvmet_fc: add missing reference in add_port jsmart2021
2017-04-19 19:36 ` Christoph Hellwig
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=20170419193625.GE18191@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;
as well as URLs for NNTP newsgroup(s).