From: Ryusuke Konishi <konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
To: Linus Torvalds
<torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Ryusuke Konishi
<konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>,
linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [GIT PULL] nilfs2 updates for 2.6.40
Date: Mon, 23 May 2011 14:35:53 +0900 (JST) [thread overview]
Message-ID: <20110523.143553.149410245.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 nilfs2 updates. A noticeable change in this
cycle is support of filesystem resizing, otherwise it's mostly
cleanups and minor fixes.
Thanks!
Ryusuke Konishi
--
The following changes since commit 349dbc3669d043e656f3ed48c7bfe073ca1c6326:
nilfs2: fix infinite loop in nilfs_palloc_freev function (2011-05-10 22:19:50 +0900)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ryusuke/nilfs2.git for-linus
Nicolas Kaiser (1):
nilfs2: merge list_del()/list_add_tail() to list_move_tail()
Ryusuke Konishi (12):
nilfs2: get rid of private page allocator
nilfs2: super root size should change depending on inode size
nilfs2: zero fill unused portion of super root block
nilfs2: add ioctl which limits range of segment to be allocated
nilfs2: add routine to move secondary super block
nilfs2: add truncation routine of segment usage file
nilfs2: implement resize ioctl
nilfs2: use empty_aops for gc-inodes
nilfs2: use list_first_entry
nilfs2: get rid of NILFS_I_NILFS
nilfs2: always set back pointer to host inode in mapping->host
nilfs2: use mark_buffer_dirty to mark btnode or meta data dirty
fs/nilfs2/alloc.c | 12 +-
fs/nilfs2/bmap.c | 4 +-
fs/nilfs2/btnode.c | 19 +--
fs/nilfs2/btnode.h | 4 -
fs/nilfs2/btree.c | 38 +++---
fs/nilfs2/cpfile.c | 24 ++--
fs/nilfs2/dat.c | 4 +-
fs/nilfs2/file.c | 1 -
fs/nilfs2/gcinode.c | 25 ++---
fs/nilfs2/ifile.c | 4 +-
fs/nilfs2/inode.c | 23 +++-
fs/nilfs2/ioctl.c | 61 ++++++++++
fs/nilfs2/mdt.c | 8 +-
fs/nilfs2/mdt.h | 9 +--
fs/nilfs2/nilfs.h | 7 +-
fs/nilfs2/page.c | 79 +------------
fs/nilfs2/page.h | 7 +-
fs/nilfs2/recovery.c | 12 +-
fs/nilfs2/segbuf.c | 17 +--
fs/nilfs2/segment.c | 190 ++++++--------------------------
fs/nilfs2/segment.h | 2 -
fs/nilfs2/sufile.c | 274 +++++++++++++++++++++++++++++++++++++++++----
fs/nilfs2/sufile.h | 4 +-
fs/nilfs2/super.c | 131 +++++++++++++++++++++-
fs/nilfs2/the_nilfs.c | 24 +++-
fs/nilfs2/the_nilfs.h | 2 +
include/linux/nilfs2_fs.h | 4 +-
27 files changed, 603 insertions(+), 386 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
reply other threads:[~2011-05-23 5:35 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=20110523.143553.149410245.ryusuke@osrg.net \
--to=konishi.ryusuke-zyj7fxus5i5l9jvzuh4aog@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.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).