linux-kernel - Re: intel-iommu: Add for_each_iommu() and for_each_active

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]

Date:	Wed, 8 Apr 2009 13:00:37 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	David Woodhouse <dwmw2@...radead.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Steven Rostedt <rostedt@...dmis.org>
Subject: Re: intel-iommu: Add for_each_iommu() and for_each_active_iommu()
	macros

* David Woodhouse <dwmw2@...radead.org> wrote:

> On Mon, 2009-04-06 at 17:59 -0700, Andrew Morton wrote:
> > 
> > Three days old?  Never been in linux-next afaict.
> > 
> > Please don't do that.
> 
> Sorry about that. There was some confusion about whether it was 
> going via Ingo's or my tree, and it ended up in neither. It 
> depended on certain things in Ingo's tree, so I couldn't easily 
> add it to my tree any earlier.

Well, they could have ended up in the x86 tree or in the IOMMU tree, 
but the patches were all very late and went through various review 
rounds with me so they had no chance to end up there in a finished 
state before the merge window.

I didnt mind you pushing them to Linus separately and gave an 
Acked-by for the bits and for that merge route, but all the usual 
protocols still have to be followed if you do that: review, testing, 
proper exposure.

	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/