For the m32r architecture, is there a reason not to use the generic bug.h
definition?

Signed-off-by: Daniel Dickman <[EMAIL PROTECTED]>

--- linux-2.6.11-rc4/include/asm-m32r/bug.h     2004-12-24 16:34:01.000000000
-0500
+++ linux/include/asm-m32r/bug.h        2005-02-13 03:39:39.775236000 -0500
@@ -1,22 +1,4 @@
 #ifndef _M32R_BUG_H
 #define _M32R_BUG_H
-
-#define BUG()  do { \
-       printk("kernel BUG at %s:%d!\n", __FILE__, __LINE__); \
-} while (0)
-
-#define PAGE_BUG(page) do { BUG(); } while (0)
-
-#define BUG_ON(condition) \
-       do { if (unlikely((condition)!=0)) BUG(); } while(0)
-
-#define WARN_ON(condition) do { \
-       if (unlikely((condition)!=0)) { \
-               printk("Badness in %s at %s:%d\n", __FUNCTION__, \
-               __FILE__, __LINE__); \
-               dump_stack(); \
-       } \
-} while (0)
-
-#endif /* _M32R_BUG_H */
-
+#include <asm-generic/bug.h>
+#endif

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

Reply via email to