linux-kernel - [PATCH] EDAC, mce_amd_inj: Include irq

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

Message-ID: <1433545654-24450-1-git-send-email-Aravind.Gopalakrishnan@amd.com>
Date:	Fri, 5 Jun 2015 18:07:34 -0500
From:	Aravind Gopalakrishnan <Aravind.Gopalakrishnan@....com>
To:	<dougthompson@...ssion.com>, <bp@...en8.de>,
	<mchehab@....samsung.com>
CC:	<linux-edac@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
	<fengguang.wu@...el.com>, <kbuild-all@...org>
Subject: [PATCH] EDAC, mce_amd_inj: Include irq_vectors header to fix build errors

Even though !CONFIG_SMP and MCE injection are practically mutually
exclusive, it's better to include irq_vectors.h just in case
randconfig builders out there don't set CONFIG_SMP.

When that happens, DEFERRED_ERROR_VECTOR and THRESHOLD_APIC_VECTOR
macro definitions go out of scope and kernel build will fail.

Tested the .config that broke the build against latest tip with
changes in for-next branch of bp.git and it builds fine now.

Reported-by: kbuild test robot <fengguang.wu@...el.com>
Cc: kbuild-all@...org
Signed-off-by: Aravind Gopalakrishnan <Aravind.Gopalakrishnan@....com>
---
 drivers/edac/mce_amd_inj.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/edac/mce_amd_inj.c b/drivers/edac/mce_amd_inj.c
index 3f7217f..3e1b53f 100644
--- a/drivers/edac/mce_amd_inj.c
+++ b/drivers/edac/mce_amd_inj.c
@@ -18,6 +18,7 @@
 #include <linux/string.h>
 #include <linux/uaccess.h>
 #include <asm/mce.h>
+#include <asm/irq_vectors.h>
 
 #include "mce_amd.h"
 
-- 
2.4.0

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