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]

Message-Id: <1239066583.22733.258.camel@macbook.infradead.org>
Date:	Mon, 06 Apr 2009 18:09:43 -0700
From:	David Woodhouse <dwmw2@...radead.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
	Steven Rostedt <rostedt@...dmis.org>
Subject: Re: intel-iommu: Add for_each_iommu() and for_each_active_iommu()
 macros

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.

I'm unconvinced by the fix -- can we find a way to fix the if() macro so
that normal (if fugly) C code like this doesn't doesn't need this kind
of workaround?

(Yes, it's fugly. But the original was worse IMHO:
https://lists.linux-foundation.org/pipermail/iommu/attachments/20090327/31f84f7d/attachment.txt )

-- 
dwmw2

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