From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH resend 0/3] couple of nvme patches resend
Date: Mon, 15 Jan 2018 16:22:21 +0100 [thread overview]
Message-ID: <20180115152221.GB9121@lst.de> (raw)
In-Reply-To: <20180114103902.6413-1-sagi@grimberg.me>
On Sun, Jan 14, 2018@12:38:59PM +0200, Sagi Grimberg wrote:
> Seems these got positive feedback (informally) but were left behind..
Thanks, applied to nvme-4.6.
prev parent reply other threads:[~2018-01-15 15:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-14 10:38 [PATCH resend 0/3] couple of nvme patches resend Sagi Grimberg
2018-01-14 10:39 ` [PATCH resend 1/3] nvme-pci: serialize pci resets Sagi Grimberg
2018-01-14 10:39 ` [PATCH resend 2/3] nvme-pci: allocate device queues storage space at probe Sagi Grimberg
2018-01-23 16:06 ` Keith Busch
2018-01-14 10:39 ` [PATCH resend 3/3] nvme-core/loop/rdma: Host delete_work and reset_work on separate workqueues Sagi Grimberg
2018-01-15 15:22 ` 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=20180115152221.GB9121@lst.de \
--to=hch@lst.de \
/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).