linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: Mike Fedyk <mfedyk@matchmail.com>
Cc: Andrew Morton <akpm@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>, John Stultz <johnstul@us.ibm.com>
Subject: Re: Compile problem with CONFIG_X86_CYCLONE_TIMER Re: 2.6.0-test3-mm2
Date: 16 Aug 2003 13:32:22 -0700	[thread overview]
Message-ID: <1061065941.31662.35.camel@nighthawk> (raw)
In-Reply-To: <20030815203620.GO1027@matchmail.com>

[-- Attachment #1: Type: text/plain, Size: 838 bytes --]

On Fri, 2003-08-15 at 13:36, Mike Fedyk wrote:
> On Fri, Aug 15, 2003 at 01:23:22PM -0700, Mike Fedyk wrote:
> > On Fri, Aug 15, 2003 at 12:38:34PM -0700, Mike Fedyk wrote:
> > > arch/i386/kernel/timers/timer_cyclone.c: In function `init_cyclone':
> > > arch/i386/kernel/timers/timer_cyclone.c:157: `FIX_CYCLONE_TIMER' undeclared (first use in this function)
> > > arch/i386/kernel/timers/timer_cyclone.c:157: (Each undeclared identifier is reported only once
> > > arch/i386/kernel/timers/timer_cyclone.c:157: for each function it appears in.)
> > >

I couldn't replicate the problem, but I suspect this fix is correct in
any case.  If this doesn't fix it, please post your config.  

John, I imagine that you probably haven't always had CONFIG_X86_CYCLONE,
and this was just a leftover from then.  

-- 
Dave Hansen
haveblue@us.ibm.com

[-- Attachment #2: cyclone-fixmap-2.6.0-test3-mm2-0.patch --]
[-- Type: text/plain, Size: 385 bytes --]

--- linux-2.6.0-test3-mm2-clean/include/asm-i386/fixmap.h	Sat Aug 16 13:18:22 2003
+++ linux-2.6.0-test3-mm2-cyclonefix/include/asm-i386/fixmap.h	Sat Aug 16 13:28:30 2003
@@ -73,7 +73,7 @@
 	FIX_TSS_0,
 	FIX_ENTRY_TRAMPOLINE_1,
 	FIX_ENTRY_TRAMPOLINE_0,
-#ifdef CONFIG_X86_SUMMIT
+#ifdef CONFIG_X86_CYCLONE
 	FIX_CYCLONE_TIMER, /*cyclone timer register*/
 	FIX_VSTACK_HOLE_2,
 #endif 

  reply	other threads:[~2003-08-16 20:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-13  8:31 2.6.0-test3-mm2 Andrew Morton
2003-08-13  9:11 ` How to use hugetlb for the text of a program ? dada1
2003-08-13  9:26   ` Andrew Morton
2003-08-13 12:42     ` dada1
2003-08-13  9:22 ` 2.6.0-test3-mm2 hugang
2003-08-13 10:48   ` 2.6.0-test3-mm2 Andrew Morton
2003-08-13 13:02 ` 2.6.0-test3-mm2 Con Kolivas
2003-08-13 13:35   ` 2.6.0-test3-mm2 Luiz Capitulino
2003-08-13 13:36   ` 2.6.0-test3-mm2 Luiz Capitulino
2003-08-13 14:32   ` 2.6.0-test3-mm2 Hugh Dickins
2003-08-13 16:16     ` 2.6.0-test3-mm2 Martin J. Bligh
2003-08-13 16:18     ` 2.6.0-test3-mm2 Luiz Capitulino
2003-08-15 19:38 ` Compile problem with CONFIG_X86_CYCLONE_TIMER 2.6.0-test3-mm2 Mike Fedyk
2003-08-15 20:23   ` Mike Fedyk
2003-08-15 20:36     ` Mike Fedyk
2003-08-16 20:32       ` Dave Hansen [this message]
2003-08-27  1:08         ` Compile problem with CONFIG_X86_CYCLONE_TIMER Re: 2.6.0-test4-mm1 Mike Fedyk
2003-08-27  4:41           ` Dave Hansen
2003-08-27 16:00             ` Mike Fedyk
2003-08-27 16:15               ` Dave Hansen
2003-08-17 20:37 ` 2.6.0-test3-mm2 Peter Osterlund

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=1061065941.31662.35.camel@nighthawk \
    --to=haveblue@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mfedyk@matchmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).