From: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-kernel@vger.kernel.org, konishi.ryusuke@lab.ntt.co.jp
Subject: Pull request for nilfs2 tree
Date: Mon, 13 Apr 2009 17:29:31 +0900 (JST) [thread overview]
Message-ID: <20090413.172931.45933263.ryusuke@osrg.net> (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(-)
next reply other threads:[~2009-04-13 8:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-13 8:29 Ryusuke Konishi [this message]
2009-04-13 21:55 ` Stephen Rothwell
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=20090413.172931.45933263.ryusuke@osrg.net \
--to=konishi.ryusuke@lab.ntt.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®