From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
Randy Dunlap <randy.dunlap@oracle.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Jeremy Fitzhardinge <Jeremy.Fitzhardinge@citrix.com>
Subject: Re: linux-next: Tree for July 27 (xen)
Date: Wed, 28 Jul 2010 16:06:26 +0100 [thread overview]
Message-ID: <alpine.DEB.2.00.1007281601380.19809@kaball-desktop> (raw)
In-Reply-To: <4C504345.2050204@goop.org>
On Wed, 28 Jul 2010, Jeremy Fitzhardinge wrote:
> On 07/28/2010 06:11 AM, Stefano Stabellini wrote:
> > On Tue, 27 Jul 2010, Randy Dunlap wrote:
> >> Stephen Rothwell wrote:
> >>> Hi all,
> >>>
> >>> Changes since 20100726:
> >>>
> >>>
> >>> The xen tree lost its build problems but gained a conflict against Linus'
> >>> tree.
> >> when X86_32=y, SMP=n, X86_LOCAL_APIC=n:
> >>
> >> drivers/built-in.o: In function `xen_callback_vector':
> >> (.text+0x41238): undefined reference to `first_system_vector'
> >>
> >> alloc_intr_gate() calls alloc_system_vector(), which uses first_system_vector.
> > this patch should solve the issue:
>
> So this is a generic x86 build problem?
>
It is, but nobody else is calling alloc_intr_gate with X86_LOCAL_APIC=n;
being a static inline function it didn't cause any problems.
next prev parent reply other threads:[~2010-07-28 15:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 6:07 linux-next: Tree for July 27 Stephen Rothwell
2010-07-27 7:24 ` Jaswinder Singh Rajput
2010-07-27 7:28 ` Stephen Rothwell
2010-07-27 18:35 ` Alex Elder
2010-07-28 1:24 ` Stephen Rothwell
2010-07-27 18:38 ` linux-next: Tree for July 27 (xen) Randy Dunlap
2010-07-28 13:11 ` Stefano Stabellini
2010-07-28 14:48 ` Jeremy Fitzhardinge
2010-07-28 15:06 ` Stefano Stabellini [this message]
2010-07-28 15:47 ` Randy Dunlap
2010-07-27 19:21 ` [PATCH -next] staging/line6: needs to select SND_PCM Randy Dunlap
2010-07-28 13:59 ` Takashi Iwai
2010-07-28 15:19 ` Greg KH
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=alpine.DEB.2.00.1007281601380.19809@kaball-desktop \
--to=stefano.stabellini@eu.citrix.com \
--cc=Jeremy.Fitzhardinge@citrix.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
/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®