Re: upstream merge status for 2.6.35, .36?

[Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>]

On Wed, Aug 04, 2010 at 11:38:48PM +0200, Josip Rodin wrote:
> 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

Aug 14/15th.

> closed for .36?

Yes.