From: willy@linux.intel.com (Matthew Wilcox)
Subject: Tree updated 2013-05-17
Date: Fri, 17 May 2013 09:35:17 -0400 [thread overview]
Message-ID: <20130517133517.GO6057@linux.intel.com> (raw)
I've pulled in a few fixes:
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
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()
I'll ask Linus to pull them next week, and they should be in 3.10.
I've also set up separate branches for "just fixes" (fixes-3.10) and
features / improvements that aren't bug fixes (master). Right now,
they're the same, but I would expect them to diverge fairly shortly.
next reply other threads:[~2013-05-17 13:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 13:35 Matthew Wilcox [this message]
2013-05-29 21:04 ` Tree updated 2013-05-29 Matthew Wilcox
2013-05-29 20:44 ` Keith Busch
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=20130517133517.GO6057@linux.intel.com \
--to=willy@linux.intel.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 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).