public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Mike Travis <travis@sgi.com>
Cc: Yinghai Lu <Yinghai.Lu@Sun.COM>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: fix x86_32 builds for summit and es7000 arch's
Date: Tue, 6 Jan 2009 13:28:20 +0100	[thread overview]
Message-ID: <20090106122820.GA10319@elte.hu> (raw)
In-Reply-To: <4962AF55.9060704@sgi.com>


* Mike Travis <travis@sgi.com> wrote:

> Mike Travis wrote:
> > Yinghai Lu wrote:
> >> In file included from arch/x86/mach-generic/summit.c:16:
> >> /home/yhlu/xx/xx/kernel/tip/linux-2.6/arch/x86/include/asm/summit/apic.h:
> >> In function ‘cpu_mask_to_apicid_and’:
> >> /home/yhlu/xx/xx/kernel/tip/linux-2.6/arch/x86/include/asm/summit/apic.h:179:
> >> error: ‘GFP_ATOMIC’ undeclared (first use in this function)
> >> /home/yhlu/xx/xx/kernel/tip/linux-2.6/arch/x86/include/asm/summit/apic.h:179:
> >> error: (Each undeclared identifier is reported only once
> >> /home/yhlu/xx/xx/kernel/tip/linux-2.6/arch/x86/include/asm/summit/apic.h:179:
> >> error: for each function it appears in.)
> >>
> >> YH
> >>
> > 
> > Hi Yinghai,
> > 
> > Thanks for catching this, I'm looking at it now.  We had a bit of a power
> > problem here and have been down for a while.
> > 
> > Thanks,
> > Mike
> 
> Subject: x86: fix x86_32 builds for summit and es7000 arch's
> 
> Impact: fix build errors on x86_32
>
> Fix the following build errors reported by Yinghai Lu:

applied to tip/cpus4096, thanks guys!

	Ingo

      reply	other threads:[~2009-01-06 12:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-05 23:05 compiling error Yinghai Lu
2009-01-06  0:35 ` Mike Travis
2009-01-06  1:09   ` [PATCH] x86: fix x86_32 builds for summit and es7000 arch's Mike Travis
2009-01-06 12:28     ` Ingo Molnar [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=20090106122820.GA10319@elte.hu \
    --to=mingo@elte.hu \
    --cc=Yinghai.Lu@Sun.COM \
    --cc=linux-kernel@vger.kernel.org \
    --cc=travis@sgi.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