From: Borislav Petkov <bp@amd64.org>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
EDAC devel <linux-edac@vger.kernel.org>, X86-ML <x86@kernel.org>,
Borislav Petkov <borislav.petkov@amd.com>
Subject: [PATCH] EDAC: Correct Kconfig dependencies
Date: Wed, 10 Aug 2011 14:43:30 +0200 [thread overview]
Message-ID: <1312980210-3692-1-git-send-email-bp@amd64.org> (raw)
In-Reply-To: <4E41055F.9010900@redhat.com>
From: Borislav Petkov <borislav.petkov@amd.com>
Both AMD and Intel i7 EDAC drivers use MCE features and are thus
dependent of this functionality present in the kernel. Express this in
Kconfig so that randconfig builds don't break.
Reported-by: Randy Dunlap <rdunlap@xenotime.net>
Signed-off-by: Borislav Petkov <borislav.petkov@amd.com>
---
drivers/edac/Kconfig | 5 ++---
1 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/edac/Kconfig b/drivers/edac/Kconfig
index f888fb5..d057d6c 100644
--- a/drivers/edac/Kconfig
+++ b/drivers/edac/Kconfig
@@ -41,7 +41,7 @@ config EDAC_DEBUG
config EDAC_DECODE_MCE
tristate "Decode MCEs in human-readable form (only on AMD for now)"
- depends on CPU_SUP_AMD && X86_MCE
+ depends on CPU_SUP_AMD && X86_MCE_AMD
default y
---help---
Enable this option if you want to decode Machine Check Exceptions
@@ -170,8 +170,7 @@ config EDAC_I5400
config EDAC_I7CORE
tristate "Intel i7 Core (Nehalem) processors"
- depends on EDAC_MM_EDAC && PCI && X86
- select EDAC_MCE
+ depends on EDAC_MM_EDAC && PCI && X86 && X86_MCE_INTEL
help
Support for error detection and correction the Intel
i7 Core (Nehalem) Integrated Memory Controller that exists on
--
1.7.4.rc2
next prev parent reply other threads:[~2011-08-10 12:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-08 2:25 Linux 3.1-rc1 Linus Torvalds
2011-08-08 20:59 ` Linux 3.1-rc1 (i7core_edac build error) Randy Dunlap
2011-08-08 21:31 ` Borislav Petkov
2011-08-08 21:37 ` Randy Dunlap
2011-08-09 10:01 ` Mauro Carvalho Chehab
2011-08-10 12:43 ` Borislav Petkov [this message]
2011-08-10 17:14 ` [PATCH] EDAC: Correct Kconfig dependencies Randy Dunlap
2011-08-11 16:26 ` Borislav Petkov
2011-08-08 21:35 ` Linux 3.1-rc1 (staging/comedi) Randy Dunlap
2011-08-08 21:37 ` Randy Dunlap
2011-08-08 21:51 ` Greg KH
2011-08-08 23:32 ` Randy Dunlap
2011-08-10 18:22 ` [PATCH mainline] xen: xen-selfballoon.c needs more header files Randy Dunlap
2011-08-10 19:20 ` Konrad Rzeszutek Wilk
2011-08-10 19:23 ` Linux 3.1-rc1 (nfs/pnfs and drivers/md) Randy Dunlap
2011-08-11 0:35 ` Peng Tao
2011-08-11 0:58 ` Randy Dunlap
2011-08-11 1:10 ` Linus Torvalds
2011-08-11 3:26 ` tao.peng
2011-08-11 6:06 ` Christoph Hellwig
2011-08-11 6:21 ` tao.peng
2011-08-11 10:11 ` Benny Halevy
2011-08-11 18:44 ` Boaz Harrosh
2011-08-11 21:10 ` [PATCH] pnfs: Automatically select blocks & objects layouts Boaz Harrosh
2011-08-11 21:29 ` [PATCH v2] " Boaz Harrosh
2011-08-11 21:43 ` Randy Dunlap
2011-08-11 21:53 ` Boaz Harrosh
2011-08-11 22:13 ` [PATCH] " Jim Rees
2011-08-11 23:47 ` Peng Tao
2011-08-11 15:41 ` Linux 3.1-rc1 (nfs/pnfs and drivers/md) Randy Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1312980210-3692-1-git-send-email-bp@amd64.org \
--to=bp@amd64.org \
--cc=borislav.petkov@amd.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=rdunlap@xenotime.net \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome