summaryrefslogtreecommitdiffstats
path: root/include/linux
diff options
context:
space:
mode:
authorLen Brown <len.brown@intel.com>2008-10-22 23:19:45 -0400
committerLen Brown <len.brown@intel.com>2008-10-22 23:19:45 -0400
commit6b3c4f8b9c417541c561155bf6b2150a81b5d5eb (patch)
tree64d1a60ade7e5f2a0ad0e2d701b57f51aabd1f3d /include/linux
parent3fa8749e584b55f1180411ab1b51117190bac1e5 (diff)
parent2fd47094f92fa2bdbf99be33294a7b6b97785a70 (diff)
downloadop-kernel-dev-6b3c4f8b9c417541c561155bf6b2150a81b5d5eb.zip
op-kernel-dev-6b3c4f8b9c417541c561155bf6b2150a81b5d5eb.tar.gz
Merge branch 'FW_BUG' into test
Diffstat (limited to 'include/linux')
-rw-r--r--include/linux/kernel.h24
1 files changed, 24 insertions, 0 deletions
diff --git a/include/linux/kernel.h b/include/linux/kernel.h
index 2651f80..0b19848 100644
--- a/include/linux/kernel.h
+++ b/include/linux/kernel.h
@@ -190,6 +190,30 @@ extern int kernel_text_address(unsigned long addr);
struct pid;
extern struct pid *session_of_pgrp(struct pid *pgrp);
+/*
+ * FW_BUG
+ * Add this to a message where you are sure the firmware is buggy or behaves
+ * really stupid or out of spec. Be aware that the responsible BIOS developer
+ * should be able to fix this issue or at least get a concrete idea of the
+ * problem by reading your message without the need of looking at the kernel
+ * code.
+ *
+ * Use it for definite and high priority BIOS bugs.
+ *
+ * FW_WARN
+ * Use it for not that clear (e.g. could the kernel messed up things already?)
+ * and medium priority BIOS bugs.
+ *
+ * FW_INFO
+ * Use this one if you want to tell the user or vendor about something
+ * suspicious, but generally harmless related to the firmware.
+ *
+ * Use it for information or very low priority BIOS bugs.
+ */
+#define FW_BUG "[Firmware Bug]: "
+#define FW_WARN "[Firmware Warn]: "
+#define FW_INFO "[Firmware Info]: "
+
#ifdef CONFIG_PRINTK
asmlinkage int vprintk(const char *fmt, va_list args)
__attribute__ ((format (printf, 1, 0)));
OpenPOWER on IntegriCloud