From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH 0/4] nvme_fcloop: abort and isr context changes
Date: Mon, 4 Dec 2017 12:19:05 -0800 [thread overview]
Message-ID: <20171204201905.GA11628@infradead.org> (raw)
In-Reply-To: <20171130004733.19330-1-jsmart2021@gmail.com>
Thanks,
applied to nvme-4.16.
prev parent reply other threads:[~2017-12-04 20:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 0:47 [PATCH 0/4] nvme_fcloop: abort and isr context changes James Smart
2017-11-30 0:47 ` [PATCH 1/4] nvme_fcloop: fix abort race condition James Smart
2017-11-30 0:47 ` [PATCH 2/4] nvme_fcloop: disassocate local port structs James Smart
2017-11-30 0:47 ` [PATCH 3/4] nvme_fcloop: rework to remove xxx_IN_ISR feature flags James Smart
2017-11-30 0:47 ` [PATCH 4/4] nvme_fcloop: refactor host/target io job access James Smart
2017-12-04 20:19 ` Christoph Hellwig [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=20171204201905.GA11628@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