From: Ryusuke Konishi <ryusuke@osrg.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>
Subject: [GIT PULL] nilfs2 updates for 2.6.34
Date: Wed, 03 Mar 2010 23:10:05 +0900 (JST) [thread overview]
Message-ID: <20100303.231005.71011379.ryusuke@osrg.net> (raw)
Hi Linus,
please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/ryusuke/nilfs2.git for-linus
to receive the following updates. There are minor fixes, several
cleanups, and a new mount option to use discard/trim for sector ranges
nilfs GC freed.
Thanks!
Ryusuke Konishi
--
The following changes since commit 724e6d3fe8003c3f60bf404bf22e4e331327c596:
Linus Torvalds (1):
Linux 2.6.33-rc8
Jiro SEKIBA (4):
nilfs2: issue discard request after cleaning segments
nilfs2: delete unnecessary condition in nilfs_dat_translate
nilfs2: delete unnecessary condition in load_segment_summary
nilfs2: add reader's lock for cno in nilfs_ioctl_sync
Ryusuke Konishi (5):
nilfs2: use mnt_want_write in ioctls where write access is needed
nilfs2: fix potential hang in nilfs_error on errors=remount-ro
nilfs2: get rid of nilfs_segctor_req struct
nilfs2: get rid of s_dirt flag use
nilfs2: move iterator to write log into segment buffer
Documentation/filesystems/nilfs2.txt | 3 +
fs/nilfs2/dat.c | 3 +-
fs/nilfs2/ioctl.c | 66 ++++++++++++++-----
fs/nilfs2/recovery.c | 41 +++---------
fs/nilfs2/segbuf.c | 18 +++++
fs/nilfs2/segbuf.h | 5 +-
fs/nilfs2/segment.c | 120 ++++++++++++++++++----------------
fs/nilfs2/segment.h | 2 +
fs/nilfs2/super.c | 15 +++--
fs/nilfs2/the_nilfs.c | 38 +++++++++++
fs/nilfs2/the_nilfs.h | 3 +
include/linux/nilfs2_fs.h | 1 +
12 files changed, 199 insertions(+), 116 deletions(-)
reply other threads:[~2010-03-03 14:10 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=20100303.231005.71011379.ryusuke@osrg.net \
--to=ryusuke@osrg.net \
--cc=konishi.ryusuke@lab.ntt.co.jp \
--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
Powered by JetHome