From: Shaohua Li <shaohua.li@intel.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: akpm <akpm@osdl.org>
Subject: Trival patch: CPU hotplug some HPET routines
Date: Fri, 24 Jun 2005 11:25:02 +0800 [thread overview]
Message-ID: <1119583502.4277.3.camel@linux-hp.sh.intel.com> (raw)
Hi,
This is a trival patch. With hpet enabled, cpu hotplug uses some
routines marked with __init.
Signed-off-by: Shaohua Li<shaohua.li@intel.com>
---
linux-2.6.12-mm1-root/arch/i386/kernel/time_hpet.c | 2 +-
linux-2.6.12-mm1-root/arch/i386/kernel/timers/common.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff -puN arch/i386/kernel/time_hpet.c~timer_initcall_cleanup arch/i386/kernel/time_hpet.c
--- linux-2.6.12-mm1/arch/i386/kernel/time_hpet.c~timer_initcall_cleanup 2005-06-23 10:58:20.000000000 +0800
+++ linux-2.6.12-mm1-root/arch/i386/kernel/time_hpet.c 2005-06-23 10:58:20.000000000 +0800
@@ -50,7 +50,7 @@ static void hpet_writel(unsigned long d,
* comparator value and continue. Next tick can be caught by checking
* for a change in the comparator value. Used in apic.c.
*/
-static void __init wait_hpet_tick(void)
+static void __devinit wait_hpet_tick(void)
{
unsigned int start_cmp_val, end_cmp_val;
diff -puN arch/i386/kernel/timers/common.c~timer_initcall_cleanup arch/i386/kernel/timers/common.c
--- linux-2.6.12-mm1/arch/i386/kernel/timers/common.c~timer_initcall_cleanup 2005-06-23 10:58:20.000000000 +0800
+++ linux-2.6.12-mm1-root/arch/i386/kernel/timers/common.c 2005-06-23 10:58:20.000000000 +0800
@@ -86,7 +86,7 @@ bad_ctc:
#define CALIBRATE_CNT_HPET (5 * hpet_tick)
#define CALIBRATE_TIME_HPET (5 * KERNEL_TICK_USEC)
-unsigned long __init calibrate_tsc_hpet(unsigned long *tsc_hpet_quotient_ptr)
+unsigned long __devinit calibrate_tsc_hpet(unsigned long *tsc_hpet_quotient_ptr)
{
unsigned long tsc_startlow, tsc_starthigh;
unsigned long tsc_endlow, tsc_endhigh;
_
reply other threads:[~2005-06-24 3:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1119583502.4277.3.camel@linux-hp.sh.intel.com \
--to=shaohua.li@intel.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.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