> > > The overall result is basically the same, but it's way simpler to look > > > at obvious and well done patches than checking whether a subtle copy > > > and paste bug happened in 3/5 of the first version. Copy and paste is > > > the #1 cause for subtle bugs. :) > > > > > > I'm waiting for the ack of Xen folks before taking it into tip.
In case you are waiting for that - Acked-by: Konrad Rzeszutek Wilk <konrad.w...@oracle.com> > > > > I've some extra patches that modify the new "paginig_init" in the Xen > > code that I am going to propose for v3.7 - so will have some merge > > conflicts. Let me figure that out and also run this set of patches > > (and also the previous one .. which I think you didn't have a > > chance to look since you were on vacation?) on an overnight > > Which previous one ? > > > test to make sure there are no fallout. > > > > With the merge issues that are going to prop up (x86 tip tree > > and my tree in linux-next) should I just take these patches > > in my tree with your Ack? Or should I just ingest your tiptree > > in my tree and that way solve the merge issue? What's your > > preference! > > Having it in tip in an extra branch which you pull into your > tree. That's the easiest one. ping? Which branch should I pull? > > Thanks, > > tglx -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
