From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH] nvme-fabrics: add-remove ctrl repeat fix
Date: Mon, 4 Jul 2016 01:48:17 -0700 [thread overview]
Message-ID: <20160704084817.GA1217@infradead.org> (raw)
In-Reply-To: <1467400412-13052-1-git-send-email-james_p_freyensee@linux.intel.com>
On Fri, Jul 01, 2016@12:13:32PM -0700, Jay Freyensee wrote:
> Fix by: "Ming Lin" <mlin at kernel.org>
So is this authored by you or by Ming? In the latter case this
should be a
From: "Ming Lin" <mlin@kernel.org>
The patch itself looks fine, I'll queue it up after we've sorted
out the above question, thanks to both of you.
But I think we'll also need a kref_get_unless_zero in __nvmf_host_find
to make this code fully correct, I'll prepare a patch for that.
next prev parent reply other threads:[~2016-07-04 8:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 19:13 [PATCH] nvme-fabrics: add-remove ctrl repeat fix Jay Freyensee
2016-07-04 8:48 ` Christoph Hellwig [this message]
2016-07-08 15:56 ` J Freyensee
2016-07-12 23:15 ` J Freyensee
2016-07-12 23:38 ` Jens Axboe
2016-07-13 16:16 ` J Freyensee
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=20160704084817.GA1217@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).