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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [PATCH] smp_call_function_single() should be a macro on UP
    • From: Al Viro <[email protected]>
  • Re: [PATCH] smp_call_function_single() should be a macro on UP
    • From: David Miller <[email protected]>
  • Re: [PATCH] smp_call_function_single() should be a macro on UP
    • From: Ben Dooks <[email protected]>

• Prev by Date: Re: [PATCH][RFC] 4K stacks default, not a debug thing any more...?
• Next by Date: Re: [PATCH][RFC] 4K stacks default, not a debug thing any more...?
• Previous by thread: Re: [PATCH] smp_call_function_single() should be a macro on UP
• Next by thread: [git patches 1/2] warnings: attack valid cases spotted by warnings
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]