All of lore.kernel.org
 help / color / mirror / Atom feed
From: swise@opengridcomputing.com (Steve Wise)
Subject: [PATCH v5 0/6] nvme-rdma device removal fixes
Date: Mon, 12 Sep 2016 09:49:32 -0500	[thread overview]
Message-ID: <00ee01d20d04$df3e2d70$9dba8850$@opengridcomputing.com> (raw)
In-Reply-To: <89eb2382-9a2f-48d1-c9fd-0c018e07cd9f@grimberg.me>

> > Doug/Sagi, the first 2 iw_cxgb4 patches are included here because they're
> > needed for the testing.  While I've also submitted them to linux-rdma,
> > perhaps Sagi can merge them in nvmf-4.8-rc?  If that is acceptable
> > with everyone.
> 
> Fine with me,
> 
> Queued for the next round of rc fixes.
> 
> Thanks Steve!

Hey Sagi, Will these make 4.8-rc7?

Steve.

WARNING: multiple messages have this Message-ID (diff)
From: "Steve Wise" <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: 'Sagi Grimberg' <sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>,
	hch-jcswGhMUV9g@public.gmane.org,
	linux-nvme-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Subject: RE: [PATCH v5 0/6] nvme-rdma device removal fixes
Date: Mon, 12 Sep 2016 09:49:32 -0500	[thread overview]
Message-ID: <00ee01d20d04$df3e2d70$9dba8850$@opengridcomputing.com> (raw)
In-Reply-To: <89eb2382-9a2f-48d1-c9fd-0c018e07cd9f-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>

> > Doug/Sagi, the first 2 iw_cxgb4 patches are included here because they're
> > needed for the testing.  While I've also submitted them to linux-rdma,
> > perhaps Sagi can merge them in nvmf-4.8-rc?  If that is acceptable
> > with everyone.
> 
> Fine with me,
> 
> Queued for the next round of rc fixes.
> 
> Thanks Steve!

Hey Sagi, Will these make 4.8-rc7?

Steve.

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2016-09-12 14:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-02 16:23 [PATCH v5 0/6] nvme-rdma device removal fixes Steve Wise
2016-09-02 16:23 ` Steve Wise
2016-09-01 13:43 ` [PATCH v5 1/6] iw_cxgb4: call dev_put() on l2t allocation failure Steve Wise
2016-09-01 13:43   ` Steve Wise
2016-09-01 13:44 ` [PATCH v5 2/6] iw_cxgb4: block module unload until all ep resources are released Steve Wise
2016-09-01 13:44   ` Steve Wise
2016-09-01 16:12 ` [PATCH v5 3/6] nvme_rdma: keep a ref on the ctrl during delete/flush Steve Wise
2016-09-01 16:12   ` Steve Wise
2016-09-02 16:01 ` [PATCH v5 4/6] nvme-rdma: destroy nvme queue rdma resources on connect failure Steve Wise
2016-09-02 16:01   ` Steve Wise
2016-09-02 16:01 ` [PATCH v5 5/6] nvme-rdma: add DELETING queue flag Steve Wise
2016-09-02 16:01   ` Steve Wise
2016-09-02 16:01 ` [PATCH v5 6/6] nvme-rdma: use ib_client API to detect device removal Steve Wise
2016-09-02 16:01   ` Steve Wise
2016-09-04  7:01 ` [PATCH v5 0/6] nvme-rdma device removal fixes Sagi Grimberg
2016-09-04  7:01   ` Sagi Grimberg
2016-09-12 14:49   ` Steve Wise [this message]
2016-09-12 14:49     ` Steve Wise
2016-09-12 14:58     ` Sagi Grimberg
2016-09-12 14:58       ` Sagi Grimberg
2016-09-12 15:00       ` Steve Wise
2016-09-12 15:00         ` Steve Wise

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='00ee01d20d04$df3e2d70$9dba8850$@opengridcomputing.com' \
    --to=swise@opengridcomputing.com \
    /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.