WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] upstream merge status for 2.6.35, .36?

On Wed, Aug 04, 2010 at 04:11:00PM -0400, Konrad Rzeszutek Wilk wrote:
> > But in the latter you wrote that you don't expect #2 to get in the 2.6.36
> > merge window. Why? I saw a single tentative complaint from hpa on one
> 
> No. The #2 is right now brewing in linux-next and I am thinking to ask
> Linus to pull it next week.
> 
> > particular patch, but at the end of that subthread you all agreed that it
> > was acceptable because it's small and no worse than the currently included
> > code. Do you expect Linus to ignore the pull request because of that, or?
> 
> It is #3 that I am not expecting to get in 2.6.36 merge window, b/c
> well, I just posted it now for review and the runway is way to short for
> that.
> 
> But now re-reading my email " patches utilize the Xen-SWIOTLB library
> (http://lkml.org/lkml/2010/7/27/246) and I don't expect them to
> get in the 2.6.36 merge window." it does sound like I am refering to
> Xen-SWIOTLB, which is not what I meant. Argh. Thanks for noticing it.

Oh, no, thank you for the quick clarification :)

OK, so if #1 and #2 will hopefully get in by the time the merge window
closes (within two weeks time), the opportunity for core/dom0 is effectively
closed for .36?

-- 
     2. That which causes joy or happiness.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel