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

[Josip Rodin <joy@xxxxxxxxxxxxxx>]

On Mon, Jun 07, 2010 at 10:57:43AM -0400, Konrad Rzeszutek Wilk wrote:
> So the SWIOTLB is 1 out 3. The next component is:
> 
> 2). Xen SWIOTLB. This is the xen swiotlb code that utilizes the swiotlb
> proper that was just made generic enough to be used in this capacity.
> git://git.kernel.org/pub/scm/linux/kernel/git/konrad/swiotlb-2.6.git 
> xen-swiotlb-0.8.2
> 
> 3). and then the Xen PCI front. Which utilizes the Xen-SWIOTLB (and also
> the Xen PCI), to well, allow guests to have PCI devices passed in.
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git 
> pv/pcifront-2.6.34
> 
> The 2) and 3) are mostly Xen specific so they should be much more palpable
> than the first one.

JFTR these now look to be:

http://lkml.org/lkml/2010/8/2/289
http://lkml.org/lkml/2010/7/27/246
http://lkml.org/lkml/2010/8/4/374

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
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?

-- 
     2. That which causes joy or happiness.

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