2009/5/16 Frederic Weisbecker <fweisbec@xxxxxxxxx>: > Hi Al, Stephen, > > This patchset is subsequent to a rebase of the bkl killing in reiserfs > work rebased against -rc6. It contains only fixes. > The old topic is left unchanged but the new one reiserfs/kill-bkl-rc6 can > be pulled against -rc6 without problem. > > Also, Al, I don't know if you would still accept to apply this work in the VFS > tree. > The fact is that it becomes late in the process, we are already in -rc6 > and I would like it to be tested at least in linux-next. > > So, it's up to you. Whether you prefer to apply it and make it > available to next, or I can ask Stephen to pull directly from my tree. > > Thanks, > Frederic. > > The following changes since commit b693ba70c541a5a26eb4e8f2db5ade454afe1c74: > Frederic Weisbecker (1): > kill-the-bkl/reiserfs: unlock only when needed in search_by_key > > are available in the git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git > reiserfs/kill-bkl-rc6 Stephen, I guess Al is traveling or something. Until it finds its way to the VFS tree, it would be nice if this reiserfs bkl removal tree could be included in linux-next for testing. Could you please include it ? You can pull from: git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git reiserfs/kill-bkl-rc6 Thanks! > Frederic Weisbecker (2): > kill-the-bkl/reiserfs: acquire the inode mutex safely > kill-the-bkl/reiserfs: move the concurrent tree accesses checks per superblock > > fs/reiserfs/do_balan.c | 17 +++++------------ > fs/reiserfs/fix_node.c | 5 +---- > fs/reiserfs/journal.c | 34 ---------------------------------- > fs/reiserfs/prints.c | 4 ---- > fs/reiserfs/stree.c | 5 +---- > fs/reiserfs/xattr.c | 4 ++-- > include/linux/reiserfs_fs.h | 35 +++++++++++++++++++++++++++++++++++ > include/linux/reiserfs_fs_sb.h | 11 +++++++++++ > 8 files changed, 55 insertions(+), 60 deletions(-) > -- To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
