From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: "Glauber Costa" <gcosta@redhat.com>,
tglx@linutronix.de, hpa@zytor.com, linux-kernel@vger.kernel.org,
x86@kernel.org
Subject: Re: [GIT-PULL] time.c integration
Date: Wed, 30 Jul 2008 15:00:36 -0700 [thread overview]
Message-ID: <86802c440807301500t17108f4el2f4178154b8b164f@mail.gmail.com> (raw)
In-Reply-To: <20080730185148.GA12336@elte.hu>
On Wed, Jul 30, 2008 at 11:51 AM, Ingo Molnar <mingo@elte.hu> wrote:
>
> * Ingo Molnar <mingo@elte.hu> wrote:
>
>> Also, please do smaller steps while bringing both time_32.c and
>> time_64.c up into their final forms (and do it in multiple commits),
>> and make sure each step compiles on their respective defconfig. time.c
>> details are historically fragile, i'd not be surprised if this series
>> was the target of bisection efforts.
>
> i briefly put your current variant into tip/master, but it has build
> problems as well:
>
> arch/x86/kernel/io_apic_64.c: In function 'check_timer':
> arch/x86/kernel/io_apic_64.c:2016: error: 'timer_ack' undeclared (first use in this function)
> arch/x86/kernel/io_apic_64.c:2016: error: (Each undeclared identifier is reported only once
> arch/x86/kernel/io_apic_64.c:2016: error: for each function it appears in.)
>
> with:
>
> http://redhat.com/~mingo/misc/config-Wed_Jul_30_20_50_17_CEST_2008.bad
>
> Ingo
> --
diff --git a/include/asm-x86/timer.h b/include/asm-x86/timer.h
index d0babce..e4eb6ab 100644
--- a/include/asm-x86/timer.h
+++ b/include/asm-x86/timer.h
@@ -9,8 +9,8 @@
unsigned long long native_sched_clock(void);
unsigned long native_calibrate_tsc(void);
-#ifdef CONFIG_X86_32
extern int timer_ack;
+#ifdef CONFIG_X86_32
extern int recalibrate_cpu_khz(void);
#endif /* CONFIG_X86_32 */
next prev parent reply other threads:[~2008-07-30 22:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 1:03 Glauber Costa
2008-07-30 18:50 ` Ingo Molnar
2008-07-30 18:51 ` Ingo Molnar
2008-07-30 22:00 ` Yinghai Lu [this message]
2008-07-31 16:51 ` Ingo Molnar
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=86802c440807301500t17108f4el2f4178154b8b164f@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=gcosta@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®