linux-kernel - Re: [ANNOUNCE] iommu-2.6.git tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20081019124732.GA21115@elte.hu>
Date:	Sun, 19 Oct 2008 14:47:32 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	David Woodhouse <dwmw2@...radead.org>
Cc:	Joerg Roedel <joro@...tes.org>, iommu@...ts.linux-foundation.org,
	linux-kernel@...r.kernel.org, fenghua.yu@...el.com,
	tony.luck@...el.com, suresh.b.siddha@...el.com,
	sfr@...b.auug.org.au, andreas.herrmann3@....com,
	joseph.cihula@...el.com, akpm@...ux-foundation.org,
	jbarnes@...tuousgeek.org, tglx@...utronix.de,
	torvalds@...ux-foundation.org
Subject: Re: [ANNOUNCE] iommu-2.6.git tree

* David Woodhouse <dwmw2@...radead.org> 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://git.infradead.org/iommu-2.6.git
> > > 	http://git.infradead.org/iommu-2.6.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.

Please do not just jump into other people's workflow like that ... at 
minimum ask them what they'd prefer to do.

Firstly, it's not at all clear to me what your role in this whole matter 
is, because you've not talked to us about it. Does your interest in this 
whole topic come from the fact that you recently got hired by Intel and 
got assigned to maintain Intel's IOMMU bits two months ago?

The thing is, i havent seen a single IOMMU contribution from you in the 
last cycles, so it's weird that you now suddenly attempt to zap other 
people's trees from linux-next out of the blue ... without their 
knowledge and consent.

Your help is welcome, and as i said it before i'd encourage you to run 
your tree - and if Linus wants to pull from you directly that's his and 
Andrew's call.

At the moment IOMMU topics are a rather healthy machinery that clearly 
got new blood and new life in the past two kernel cycles. If you want to 
help out with this stuff then please start by contributing and working 
with people, not by trying to control it.

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/