From: Borislav Petkov <bp@alien8.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: [PATCH] RAS: Show Kconfig menu only on supported architectures
Date: Tue, 13 Oct 2015 20:23:09 +0200 [thread overview]
Message-ID: <20151013182308.GE20700@pd.tnic> (raw)
In-Reply-To: <20150902065039.GA10289@nazgul.tnic>
From: Borislav Petkov <bp@suse.de>
Date: Tue, 13 Oct 2015 20:18:45 +0200
Subject: [PATCH] RAS: Show Kconfig menu only on supported architectures
Make it depend on only those architectures which provide APIs to RAS
features so that it remains invisible on the remaining ones.
Requested-by: Geert Uytterhoeven <geert@linux-m68k.org>
Signed-off-by: Borislav Petkov <bp@suse.de>
---
drivers/ras/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/ras/Kconfig b/drivers/ras/Kconfig
index 4c3c67d13254..46021e15a6a6 100644
--- a/drivers/ras/Kconfig
+++ b/drivers/ras/Kconfig
@@ -1,5 +1,6 @@
menuconfig RAS
bool "Reliability, Availability and Serviceability (RAS) features"
+ depends on X86 || COMPILE_TEST
help
Reliability, availability and serviceability (RAS) is a computer
hardware engineering term. Computers designed with higher levels
--
2.3.5
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
next prev parent reply other threads:[~2015-10-13 18:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 16:52 [GIT PULL] RAS changes for v4.3 Ingo Molnar
2015-09-01 20:33 ` Geert Uytterhoeven
2015-09-02 6:50 ` Borislav Petkov
2015-10-13 18:23 ` Borislav Petkov [this message]
2015-10-13 19:05 ` [PATCH] RAS: Show Kconfig menu only on supported architectures kbuild test robot
2015-10-13 20:48 ` kbuild test robot
2015-10-16 8:16 ` kbuild test robot
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=20151013182308.GE20700@pd.tnic \
--to=bp@alien8.de \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=geert@linux-m68k.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®