Skip to contentSkip to conversation

Pull request for nilfs2 tree

DISCUSSION Ryusuke Konishi 2 participants 2 messages Apr 13, 2009

lore
Share & tools
lore
#0 lore raw

Hi dear Stephen,

Could you consider pulling the for-next branch of this tree:

git://git.kernel.org/pub/scm/linux/kernel/git/ryusuke/nilfs2.git

into linux-next, please?

This branch now includes some bug-fixes of the nilfs2 file system Linus merged in kenrel 2.6.30-rc1.

This series should be sent to Linus at an early stage, but I'd like to have it tested on the -next tree before that.

Regards,
Ryusuke Konishi
---
The following changes since commit b0cbc861a3c05e634520b049b5cc27ad6febb51f:
Linus Torvalds (1):
Revert "ACPI battery: fix async boot oops"

are available in the git repository at:

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

Ryusuke Konishi (8):
nilfs2: return f_fsid for statfs2
nilfs2: fix lockdep recursive locking warning on bmap
nilfs2: fix lockdep recursive locking warning on meta data files
nilfs2: remove module version
nilfs2: simplify handling of active state of segments fix
nilfs2: fix wrong accounting and duplicate brelse in nilfs_sufile_set_error
nilfs2: segment usage file cleanups
nilfs2: fix possible mismatch of sufile counters on recovery

 fs/nilfs2/bmap.c      |    5 +
 fs/nilfs2/nilfs.h     |    5 -
 fs/nilfs2/recovery.c  |   20 +---
 fs/nilfs2/sufile.c    |  290 ++++++++++++++++++-------------------------------
 fs/nilfs2/sufile.h    |   79 +++++++++++++-
 fs/nilfs2/super.c     |    7 +-
 fs/nilfs2/the_nilfs.c |    4 +
 7 files changed, 197 insertions(+), 213 deletions(-)
#1 lore raw

Hi,

Quoted 6 lines · On Mon, 13 Apr 2009 17:29:31 +0900 (JST) Ryusuke Konishi…

Could you consider pulling the for-next branch of this tree:

git://git.kernel.org/pub/scm/linux/kernel/git/ryusuke/nilfs2.git

into linux-next, please?

It will be in linux-next starting today.

What I tell everyone: all patches/commits in the tree/series must have been:

posted to a relevant mailing list
reviewed
unit tested
destined for the next merge window (or the current release)

*before* they are included. The linux-next tree is for integration testing and to lower the impact of conflicts between subsystems in the next merge window.

Basically, this should be just what you would send to Linus (or ask him to fetch). It is allowed to be rebased if you deem it necessary.

Signature · 3 lines
Cheers,
Stephen Rothwell                    [email protected]
http://www.canb.auug.org.au/~sfr/