From: Phil Carmody <ext-phil.2.carmody@nokia.com>
To: trivial@kernel.org
Cc: ext-phil.2.carmody@nokia.com, linux-kernel@vger.kernel.org
Subject: [PATCH 1/7] mn10300: there is no CONFIG_CALIBRATE_DELAY
Date: Sun, 3 Jul 2011 00:47:46 +0300 [thread overview]
Message-ID: <1309643272-364-2-git-send-email-ext-phil.2.carmody@nokia.com> (raw)
In-Reply-To: <1309643272-364-1-git-send-email-ext-phil.2.carmody@nokia.com>
There is, however, CONFIG_GENERIC_CALIBRATE_DELAY.
Part of a shotgun patchset; found by greps, seds, and diffs
rather than actual understanding.
Signed-off-by: Phil Carmody <ext-phil.2.carmody@nokia.com>
---
arch/mn10300/kernel/smp.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/mn10300/kernel/smp.c b/arch/mn10300/kernel/smp.c
index 9242e9f..d159b87 100644
--- a/arch/mn10300/kernel/smp.c
+++ b/arch/mn10300/kernel/smp.c
@@ -855,7 +855,7 @@ static void __init smp_callin(void)
BUG();
}
-#ifdef CONFIG_CALIBRATE_DELAY
+#ifdef CONFIG_GENERIC_CALIBRATE_DELAY
calibrate_delay(); /* Get our bogomips */
#endif
--
1.7.2.5
next prev parent reply other threads:[~2011-07-02 22:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-02 21:47 [PATCH 0/7] [TRIVIAL] Cleanup spurious CONFIGs Phil Carmody
2011-07-02 21:47 ` Phil Carmody [this message]
2011-07-02 21:47 ` [PATCH 2/7] cris: there is no CONFIG_ETRAX_KGB_PORT2 Phil Carmody
2011-07-02 21:47 ` [PATCH 3/7] xfs: there is no CONFIG_KDB_MODULES Phil Carmody
2011-07-02 21:47 ` [PATCH 4/7] ppc: there is no CONFIG_PPC47x Phil Carmody
2011-07-02 21:47 ` [PATCH 5/7] ppc: there is no CONFIG_PPC_CPU Phil Carmody
2011-07-02 21:47 ` [PATCH 6/7] nommu: there is no CONFIG_SMALL_TASKS Phil Carmody
2011-07-02 21:47 ` [PATCH 7/7] xtensa: there is no CONFIG_UNALIGNED_USER Phil Carmody
2011-07-04 4:58 ` [PATCH 3/7] xfs: there is no CONFIG_KDB_MODULES Dave Chinner
2011-07-04 8:51 ` Phil Carmody
2011-07-04 13:15 ` Lukasz
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=1309643272-364-2-git-send-email-ext-phil.2.carmody@nokia.com \
--to=ext-phil.2.carmody@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@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
all inboxes | Powered by JetHome®