Josh Triplett b06dd879f5 x86: always define BUG() and HAVE_ARCH_BUG, even with !CONFIG_BUG ... This ensures that BUG() always has a definition that causes a trap (via an undefined instruction), and that the compiler still recognizes the code following BUG() as unreachable, avoiding warnings that would otherwise appear (such as on non-void functions that don't return a value after BUG()). In addition to saving a few bytes over the generic infinite-loop implementation, this implementation traps rather than looping, which potentially allows for better error-recovery behavior (such as by rebooting). Signed-off-by: Josh Triplett <josh@joshtriplett.org> Reported-by: Arnd Bergmann <arnd@arndb.de> Acked-by: Arnd Bergmann <arnd@arndb.de> Cc: Ingo Molnar <mingo@elte.hu> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: "H. Peter Anvin" <hpa@zytor.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>		2014-04-07 16:36:10 -07:00
..
asm	x86: always define BUG() and HAVE_ARCH_BUG, even with !CONFIG_BUG	2014-04-07 16:36:10 -07:00
uapi/asm	Merge tag 'kvm-3.15-1' of git://git.kernel.org/pub/scm/virt/kvm/kvm	2014-04-02 14:50:10 -07:00