From: Matthew Wilcox <willy@linux.intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org
Subject: [GIT PULL] Fixes for the NVMe driver
Date: Fri, 28 Sep 2012 12:55:11 -0400 [thread overview]
Message-ID: <20120928165511.GB4244@linux.intel.com> (raw)
Hi Linus,
Now that actual hardware has been released (don't have any yet myself),
people are starting to want some of these fixes merged. Could I trouble
you to pull?
The following changes since commit df3481399042200792822b6243e36a95a557b57e:
NVMe: Set number of queues correctly (2012-01-11 09:22:24 -0500)
are available in the git repository at:
git://git.infradead.org/users/willy/linux-nvme.git master
for you to fetch changes up to a09115b23e2002bb35b7bfd337683f00875671ec:
NVMe: Cancel outstanding IOs on queue deletion (2012-08-07 15:56:23 -0400)
----------------------------------------------------------------
Dan Carpenter (1):
NVMe: handle allocation failure in nvme_map_user_pages()
Keith Busch (7):
NVMe: Set request queue logical block size
NVMe: Fix nvme module init when nvme_major is set
NVMe: replace nvme_ns with nvme_dev for user admin
NVMe: use namespace id for nvme_get_features
NVMe: Set block queue max sectors
NVMe: Do not set IO queue depth beyond device max
NVMe: Fix uninitialized iod compiler warning
Matthew Wilcox (3):
NVMe: Fix whitespace damage in nvme_init
NVMe: Free admin queue memory on initialisation failure
NVMe: Cancel outstanding IOs on queue deletion
Quoc-Son Anh (1):
NVMe: Use ida for nvme device instance
drivers/block/nvme.c | 153 +++++++++++++++++++++++++++++++++-----------------
include/linux/nvme.h | 2 +
2 files changed, 105 insertions(+), 50 deletions(-)
reply other threads:[~2012-09-28 16:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20120928165511.GB4244@linux.intel.com \
--to=willy@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=torvalds@linux-foundation.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