From: tip-bot for Alessandro Rubini <rubini@gnudd.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
johnstul@us.ibm.com, rubini@gnudd.com, tglx@linutronix.de,
mingo@elte.hu
Subject: [tip:x86/platform] x86/Kconfig: Cyclone-timer depends on x86-summit
Date: Mon, 5 Dec 2011 10:06:21 -0800 [thread overview]
Message-ID: <tip-f9b15df466ba923a5832c9121ad8327ccf5483ef@git.kernel.org> (raw)
In-Reply-To: <20111028224842.GA7582@mail.gnudd.com>
Commit-ID: f9b15df466ba923a5832c9121ad8327ccf5483ef
Gitweb: http://git.kernel.org/tip/f9b15df466ba923a5832c9121ad8327ccf5483ef
Author: Alessandro Rubini <rubini@gnudd.com>
AuthorDate: Sat, 29 Oct 2011 00:48:42 +0200
Committer: Ingo Molnar <mingo@elte.hu>
CommitDate: Mon, 5 Dec 2011 18:18:15 +0100
x86/Kconfig: Cyclone-timer depends on x86-summit
CONFIG_X86_CYCLONE_TIMER depends on CONFIG_X86_32_NON_STANDARD,
which forces drivers/clocksource/cyclone.c to be compiled. The
file doesn't do anything unless enabled by
arch/x86/kernel/apic/summit_32.c
Make CONFIG_X86_CYCLONE_TIMER depend by X86_SUMMIT instead, to
avoid unnecessary code in other non-standard systems.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
Cc: john stultz <johnstul@us.ibm.com>
Link: http://lkml.kernel.org/r/20111028224842.GA7582@mail.gnudd.com
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
arch/x86/Kconfig | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 9e7a361..faf39a0 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -633,7 +633,7 @@ config X86_SUMMIT_NUMA
config X86_CYCLONE_TIMER
def_bool y
- depends on X86_32_NON_STANDARD
+ depends on X86_SUMMIT
source "arch/x86/Kconfig.cpu"
prev parent reply other threads:[~2011-12-05 18:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 22:48 [PATCH] x86 Kconfig: cyclone-timer " Alessandro Rubini
2011-12-05 18:06 ` tip-bot for Alessandro Rubini [this message]
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=tip-f9b15df466ba923a5832c9121ad8327ccf5483ef@git.kernel.org \
--to=rubini@gnudd.com \
--cc=hpa@zytor.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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®