On Mon, Dec 13, 2010 at 02:40:49PM +1100, Stephen Rothwell wrote: > Hi Nick, > > On Mon, 13 Dec 2010 13:37:33 +1100 Nick Piggin <npiggin@xxxxxxxxx> wrote: > > > > Linus has suggested pretty strongly that he wants to pull this in the > > next merge window (recently, that "inodes will be RCU freed in 2.6.38" > > in an urelated discussion). As far as I know, that's what he's going to > > do. I'd like to get this some time in linux-next to improve test > > coverage (many filesystems I can't even test, so there are bound to be a > > few silly crashes). Stephen, how do I arrange that? > > Well, you ask me :-) (letting me know where the git tree is). > > I this case I would like an email from Al and/or Linus (and/or maybe > Christoph?) before I add this to linux-next as you say below that > (despite being as well tested as you can do) it does require more review > and buyin from others. Of course, if Linus is going to merge this during > the next merge window, then it really should be in linux-next as soon as > it is ready enough. Yes I would like an ack from Al to have it in linux-next. Note that wouldn't have to be an ack on the patches or agreement to merge it next window, just an "ok to get wider review and testing" type of thing. If Linus's is intending *not* to pull it, then it's not so urgent, and I might instead ask Andrew to host it in -mm for a while. I just don't want to get caught with my pants down here, because there are a good number of untested filesystems and things. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
