From: axboe@kernel.dk (Jens Axboe)
Subject: [GIT PULL] nvme fabrics patches for the next round of 4.9 rc
Date: Thu, 10 Nov 2016 22:11:27 -0700 [thread overview]
Message-ID: <56b11145-78ed-aead-2096-e14747d692fc@kernel.dk> (raw)
In-Reply-To: <044901d23ba4$a6c59e50$f450daf0$@opengridcomputing.com>
On 11/10/2016 03:49 PM, Steve Wise wrote:
>> On 11/09/2016 01:02 AM, Sagi Grimberg wrote:
>>> Hey Jens,
>>>
>>> Mostly some stability fixes for fabrics:
>>> - some memleaks, correctness and verbosity fixes from Bart
>>> - fix command delivery during queue reconnect from Christoph
>>> - nvme rdma reconnect vs io race fix from Christoph and steve
>>> - nvme rdma queue cleanup on connection failure fix from Steve
>>> - nvme rdma target error flow and queue teardown fixes
>>> - nvme rdma queue size fix from Samuel
>>> - nvmet namespace rcu race fix from Sasha
>>>
>>> please pull from:
>>>
>>> git://git.infradead.org/nvme-fabrics.git nvmf-4.9-rc
>>
>> I'm scanning the list for anything that might NOT be appropriate this
>> late in the cycle, and I see a few:
>>
>> nvme/scsi: Remove set-but-not-used variables
>> nvme-fabrics: Adjust source code indentation
>> nvme-rdma: remove redundant define
>>
>> I can pull this in for 4.10 without hesistation, but I don't want to
>> send a pull request for a fairly new feature with 3 of the commits being
>> cleanups for -rc5.
>>
>> Let me know what you want to do.
>
> It would be great to get the kato/reconnect fixes in 4.9...
Sagi? I'm sending patches for -rc5 tomorrow. Let's get this batch split
in a 4.9 and 4.10 chunk.
--
Jens Axboe
next prev parent reply other threads:[~2016-11-11 5:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 8:02 [GIT PULL] nvme fabrics patches for the next round of 4.9 rc Sagi Grimberg
2016-11-09 16:04 ` Jens Axboe
2016-11-10 22:49 ` Steve Wise
2016-11-11 5:11 ` Jens Axboe [this message]
2016-11-12 20:58 ` Sagi Grimberg
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=56b11145-78ed-aead-2096-e14747d692fc@kernel.dk \
--to=axboe@kernel.dk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.