On Thu, Sep 17, 2009 at 11:56:29AM +1000, Stephen Rothwell wrote: > Hi Frederic, > > On Thu, 17 Sep 2009 02:56:34 +0200 Frederic Weisbecker <fweisbec@xxxxxxxxx> wrote: > > > > Note that the kill-the-bkl/reiserfs tree has suffered from too much > > lock inversion problems lately. Even though I just fixed the last one > > reported, I would feel more comfortable to schedule this tree for .33 > > rather than .32 > > > > So this tree can be removed from -next and reintegrated once -rc1 is > > released, without problem. > > OK, I have removed it from today. Please let me know when it should be > readded (in case I forget - which at my age is likely :-)). Hi Stephen, Now that -rc1 has been released (well.. -rc2, or..hmm...), could you please reintegrate the tree: git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git reiserfs/kill-bkl into -next ? It is based on linux-2.6.31, I haven't merged 32-rc3 into it because there is no conflict between those and there are no dependencies against latest changes. Tell me if you need something. It's possible there are pending patches in reiserfs for .33 in -next which might conflict, I don't know. But if you need help to fix the conflicts, just tell me. Thanks! -- 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
