From: Matthew Wilcox <willy@linux.intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PULL REQUEST] NVMe driver fixes
Date: Tue, 11 Jun 2013 17:04:14 -0400 [thread overview]
Message-ID: <20130611210414.GN8211@linux.intel.com> (raw)
Hi Linus,
The following bugfixes have been accumulating for the last few weeks, and
it would be nice if they could be in 3.10.
The following changes since commit ec50f2a97a4a7098a81b40030e0bfe28bdc43740:
Merge branch 'drm-next' of git://people.freedesktop.org/~airlied/linux (2013-05-16 19:01:46 -0700)
are available in the git repository at:
git://git.infradead.org/users/willy/linux-nvme.git fixes-3.10
for you to fetch changes up to fa08a396647767abd24a9e7015cb177121d0cf15:
NVMe: Add MSI support (2013-05-31 11:45:52 -0400)
----------------------------------------------------------------
Chayan Biswas (1):
Return the result from user admin command IOCTL even in case of failure
Dan Carpenter (2):
MAINTAINERS: update NVM EXPRESS DRIVER file list
NVMe: check for integer overflow in nvme_map_user_pages()
Keith Busch (1):
NVMe: Do not cancel command multiple times
Matthew Wilcox (1):
NVMe: Use dma_set_mask() correctly
Ramachandra Rao Gajula (1):
NVMe: Add MSI support
Sachin Kamat (1):
NVMe: Remove redundant version.h header include
Vishal Verma (1):
NVMe: Fix a signedness bug in nvme_trans_modesel_get_mp
Wei Yongjun (1):
NVMe: fix error return code in nvme_submit_bio_queue()
MAINTAINERS | 2 +-
drivers/block/nvme-core.c | 62 +++++++++++++++++++++++++++++++++++----------
drivers/block/nvme-scsi.c | 3 +--
3 files changed, 50 insertions(+), 17 deletions(-)
next reply other threads:[~2013-06-11 21:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 21:04 Matthew Wilcox [this message]
2013-06-12 3:09 ` [PULL REQUEST] NVMe driver fixes Linus Torvalds
2013-06-12 6:10 ` Linus Torvalds
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=20130611210414.GN8211@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