On Thu, 2015-05-21 at 19:09 +0200, Christoph Hellwig wrote: > On Thu, May 21, 2015 at 02:34:51AM -0700, Nicholas A. Bellinger wrote: > > > > FYI, the latest code has been pushed to for-next. > > > > Will post the full series later today. > > Any chance you could do a rebase so we get to a properly reviewed series? Yes, that will be going out soon. > Between all the fixes to the RCU series and various other changes it's > very hard to verify. > > Also I'd really like to see experimental changes like the RCU code > when it was posted or the new from irq context completions could go > into separate branches and not into for-next which should be what's > ready for the merge window. > > Thanks to Fengguang's buildbot random developer branches fortunately > already get a lot of test coverage these days. Having the code in for-next early means more people are looking at it, and finding bugs. Dan already found three bugs by virtue of it being in for-next. Obviously, nothing that is not reviewed on the list will be sent upstream, but there is real value in having in flight code in for-next early. --nab -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
