From: Jens Axboe <axboe@fb.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
<linux-block@vger.kernel.org>
Subject: Re: [GIT PULL] Block fixes for 4.5-final
Date: Thu, 3 Mar 2016 14:53:34 -0700 [thread overview]
Message-ID: <20160303215334.GA15453@kernel.dk> (raw)
In-Reply-To: <56D8AC92.1070802@fb.com>
On Thu, Mar 03 2016, Jens Axboe wrote:
> >No way do I want things like cgroup writeback changes outside the
> >merge window, for example, unless it's a major performance regression
> >(with numbers) or something like that.
> >
> >No way do I want any lightnvm stuff.
> >
> >No way do I want big "cleanup" patches.
>
> I'll boil it down.
This is the boiled down version. I'll run it through some testing, and
if all goes well, send it out late tomorrow.
----------------------------------------------------------------
Christoph Hellwig (4):
nvme: set queue limits for the admin queue
nvme: fix max_segments integer truncation
block: fix blk_rq_get_max_sectors for driver private requests
block: support large requests in blk_rq_map_user_iov
Keith Busch (7):
NVMe: Don't unmap controller registers on reset
NVMe: Use IDA for namespace disk naming
NVMe: Fix namespace removal deadlock
NVMe: Simplify device reset failure
NVMe: Move error handling to failed reset handler
NVMe: Don't allow unsupported flags
NVMe: Fix 0-length integrity payload
Ming Lei (4):
block: bio: introduce helpers to get the 1st and last bvec
block: check virt boundary in bio_will_gap()
block: get the 1st and last bvec via helpers
block: merge: get the 1st and last bvec via helpers
Tejun Heo (1):
writeback: flush inode cgroup wb switches instead of pinning super_block
block/blk-map.c | 91 ++++++++++++++++++----------
block/blk-merge.c | 8 +--
drivers/nvme/host/core.c | 111 ++++++++++++++++++++++++----------
drivers/nvme/host/nvme.h | 8 +++
drivers/nvme/host/pci.c | 149 ++++++++++++++++++++++++++++------------------
fs/fs-writeback.c | 54 +++++++++++++----
fs/super.c | 1 +
include/linux/bio.h | 37 ++++++++++++
include/linux/blkdev.h | 25 +++++---
include/linux/writeback.h | 5 ++
10 files changed, 341 insertions(+), 148 deletions(-)
--
Jens Axboe
next prev parent reply other threads:[~2016-03-03 21:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 17:25 [GIT PULL] Block fixes for 4.5-final Jens Axboe
2016-03-03 20:57 ` Linus Torvalds
2016-03-03 21:11 ` Linus Torvalds
2016-03-03 21:13 ` Jens Axboe
2016-03-03 21:11 ` Jens Axboe
2016-03-03 21:20 ` Linus Torvalds
2016-03-03 21:28 ` Jens Axboe
2016-03-03 21:53 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-03-04 22:02 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=20160303215334.GA15453@kernel.dk \
--to=axboe@fb.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).