From: sagi@grimberg.me (Sagi Grimberg)
Subject: [PATCH for-4.11-rc 0/3] Fix wrong sqsize settings in fabrics
Date: Thu, 6 Apr 2017 09:15:49 +0300 [thread overview]
Message-ID: <1491459352-28200-1-git-send-email-sagi@grimberg.me> (raw)
This should have been fixed by now, but apparently it wasn't.
Sagi Grimberg (3):
nvme-loop: Fix sqsize wrong assignment based on ctrl MQES capability
nvme-rdma: Fix sqsize wrong assignment based on ctrl MQES capability
nvme-fc: Fix sqsize wrong assignment based on ctrl MQES capability
drivers/nvme/host/fc.c | 2 +-
drivers/nvme/host/rdma.c | 2 +-
drivers/nvme/target/loop.c | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
--
2.7.4
next reply other threads:[~2017-04-06 6:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 6:15 Sagi Grimberg [this message]
2017-04-06 6:15 ` [PATCH for-4.11-rc 1/3] nvme-loop: Fix sqsize wrong assignment based on ctrl MQES capability Sagi Grimberg
2017-04-06 6:15 ` [PATCH for-4.11-rc 2/3] nvme-rdma: " Sagi Grimberg
2017-04-06 6:15 ` [PATCH for-4.11-rc 3/3] nvme-fc: " Sagi Grimberg
2017-04-06 8:44 ` [PATCH for-4.11-rc 0/3] Fix wrong sqsize settings in fabrics Christoph Hellwig
2017-04-09 12:29 ` Sagi Grimberg
2017-04-09 19:58 ` Jens Axboe
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=1491459352-28200-1-git-send-email-sagi@grimberg.me \
--to=sagi@grimberg.me \
/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).