Re: [ANNOUNCE] iommu-2.6.git tree

From: David Woodhouse
Date: Sun Oct 19 2008 - 09:21:39 EST

On Sun, 2008-10-19 at 14:47 +0200, Ingo Molnar wrote:
> * David Woodhouse <dwmw2@xxxxxxxxxxxxx> wrote:
> > On Sun, 2008-10-19 at 13:12 +0200, Joerg Roedel wrote:
> > > On Sat, Oct 18, 2008 at 04:30:43PM +0100, David Woodhouse wrote:
> > > > As previously threatened, I've created an iommu-2.6.git tree:
> > > > git://
> > > >
> > >
> > > Is there a specific reason why IOMMU stuff should go to Linus
> > > without testing them in the x86 tree before? The DMA layer and IOMMU
> > > drivers are an integral component of the architecture and patches
> > > for it are best placed in the architecture tree instead of a
> > > seperate one, imho.
> >
> > This is the purpose that linux-next serves, not the x86
> > forest-of-doom.
> >
> > And I thought Ingo said his old iommu tree wasn't in there anyway?
> > [...]
> That's weird, where did you get the impression from that i "dropped" the
> "old" IOMMU tree? It's alive and kicking, all the new IOMMU code that we
> queued up and tested in the last cycle for v2.6.28 have just gone
> upstream - about 80 commits.

I cannot find the tree which allegedly already exists -- and unless I'm
mistaken, a number of patches seem to have fallen through the cracks in
the last few weeks. Since I've been asked to start looking after the
Intel IOMMU parts, it seemed sensible to make a git tree and round up
those patches.

I thought you and Thomas were working together, and I spoke to Thomas
about it during the Kernel Summit. Unless I'm very much mistaken, he
agreed that it makes sense to have a separate, real, git tree for
cross-platform IOMMU-related work.

If you want to pull that tree into yours, that's fine by me -- as long
as it gets into linux-next.

David Woodhouse Open Source Technology Centre
David.Woodhouse@xxxxxxxxx Intel Corporation

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at