From: Jens Axboe <jaxboe@fusionio.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] block/io bits for 2.6.35
Date: Thu, 08 Jul 2010 15:40:41 +0200 [thread overview]
Message-ID: <4C35D559.3040406@fusionio.com> (raw)
Hi,
Last fixes for this kernel, I believe.
This includes two regression fixes for splice, along with the writeback
fixes that we talked about a few days ago.
Please pull.
git://git.kernel.dk/linux-2.6-block.git for-linus
Changli Gao (2):
splice: direct_splice_actor() should not use pos in sd
splice: check f_mode for seekable file
Christoph Hellwig (3):
writeback: remove writeback_inodes_wbc
writeback: split writeback_inodes_wb
writeback: simplify the write back thread queue
Randy Dunlap (1):
fs-writeback: fix kernel-doc warnings
fs/afs/write.c | 1 -
fs/btrfs/extent_io.c | 2 -
fs/fs-writeback.c | 335 ++++++++++++++-----------------------------
fs/splice.c | 9 +-
include/linux/backing-dev.h | 2 -
include/linux/writeback.h | 7 +-
mm/backing-dev.c | 17 +--
mm/page-writeback.c | 3 +-
8 files changed, 122 insertions(+), 254 deletions(-)
--
Jens Axboe
reply other threads:[~2010-07-08 13:40 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=4C35D559.3040406@fusionio.com \
--to=jaxboe@fusionio.com \
--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