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: <1224488605.6770.1522.camel@macbook.infradead.org>
Date:	Mon, 20 Oct 2008 08:43:25 +0100
From:	David Woodhouse <dwmw2@...radead.org>
To:	Joerg Roedel <joro@...tes.org>
Cc:	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, mingo@...e.hu
Subject: Re: [ANNOUNCE] iommu-2.6.git tree

On Sun, 2008-10-19 at 23:14 +0200, Joerg Roedel wrote:
> This is a reason for a seperate Intel IOMMU tree which is pulled by
> Linus. But I don't think that this is a reason to take over control of
> all IOMMU development.

I have no intention of taking over control of anything, if I can
possibly avoid it. The _less_ patch-monkey work I have to do, the
happier I'll be. There's more to life than Jon's patch statistics.

I'm perfectly happy for Ingo to pull my tree into his, as I keep saying.
As long as it gets into linux-next, that's fine.

When I discussed it with Thomas a few weeks ago, he seemed to be
suggesting that creating a new tree was the best thing to do, but I'm
more than happy to adapt.

-- 
David Woodhouse                            Open Source Technology Centre
David.Woodhouse@...el.com                              Intel Corporation

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ