[GIT PULL] nilfs2 updates for 2.6.38

From: Ryusuke Konishi
Date: Mon Jan 10 2011 - 07:06:47 EST


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. The only noticeable change
is fiemap support, otherwise it's mostly cleanups and minor fixes.

Thanks!

Ryusuke Konishi
--
The following changes since commit 0c21e3aaf6ae85bee804a325aa29c325209180fd:

Merge branch 'for-next' of git://git.kernel.org/pub/scm/linux/kernel/git/hch/hfsplus (2011-01-07 17:16:27 -0800)

are available in the git repository at:

git://git.kernel.org/pub/scm/linux/kernel/git/ryusuke/nilfs2.git for-linus

Joe Perches (1):
fs/nilfs2/super.c: Use printf extension %pV

Ryusuke Konishi (10):
MAINTAINERS: add nilfs2 git tree entry
nilfs2: call nilfs_error inside bmap routines
nilfs2: mark buffer heads as delayed until the data is written to disk
nilfs2: fiemap support
nilfs2: fix a checkpatch error in page.c
nilfs2: get rid of loaded flag from nilfs object
nilfs2: simplify nilfs_mdt_freeze_buffer
nilfs2: get rid of nilfs_mount_options structure
nilfs2: do not pass sbi to functions which can get it from inode
nilfs2: unfold nilfs_dat_inode function

MAINTAINERS | 1 +
fs/nilfs2/bmap.c | 47 ++++++++++---
fs/nilfs2/btnode.c | 3 +-
fs/nilfs2/dir.c | 3 +-
fs/nilfs2/file.c | 1 +
fs/nilfs2/ifile.c | 11 +--
fs/nilfs2/inode.c | 180 ++++++++++++++++++++++++++++++++++++++++--------
fs/nilfs2/ioctl.c | 12 ++--
fs/nilfs2/mdt.c | 32 +++------
fs/nilfs2/namei.c | 1 +
fs/nilfs2/nilfs.h | 13 +---
fs/nilfs2/page.c | 86 +++++++++++++++++++++++-
fs/nilfs2/page.h | 3 +
fs/nilfs2/recovery.c | 2 +-
fs/nilfs2/sb.h | 8 --
fs/nilfs2/segment.c | 43 +++---------
fs/nilfs2/super.c | 29 +++++---
fs/nilfs2/the_nilfs.c | 6 +-
fs/nilfs2/the_nilfs.h | 3 -
19 files changed, 337 insertions(+), 147 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/