linux-kernel - Re: [PATCH] smp_call_function_single() should be a macro on UP

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] [day] [month] [year] [list]

Message-ID: <alpine.LFD.0.999.0707171707030.27353@woody.linux-foundation.org>
Date:	Tue, 17 Jul 2007 17:07:41 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Ben Dooks <ben@...ff.org>
cc:	David Miller <davem@...emloft.net>, viro@....linux.org.uk,
	linux-kernel@...r.kernel.org, avi@...ranet.com
Subject: Re: [PATCH] smp_call_function_single() should be a macro on UP



On Wed, 18 Jul 2007, Ben Dooks wrote:
> 
> This has broken _all_ ARM builds, due to using WARN_ON()
> in this header.

I think Al's patch already fixes that, since now it's back to being a 
macro, and thus the whole WARN_ON() is only visible where the macro is 
_used_, not in the header itself.

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