From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Jeremy Fitzhardinge <jeremy@goop.org>,
xen-devel@lists.xensource.com, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
linux-next@vger.kernel.org
Subject: Re: [Xen-devel] linux-next: Tree for Jun 26 (xen/x86)
Date: Wed, 26 Jun 2013 17:25:09 -0400 [thread overview]
Message-ID: <20130626212509.GB2810@phenom.dumpdata.com> (raw)
In-Reply-To: <51CB379A.7010606@infradead.org>
On Wed, Jun 26, 2013 at 11:48:58AM -0700, Randy Dunlap wrote:
> On 06/26/13 01:06, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20130625:
> >
>
> CONFIG_SMP is not set
> CONFIG_X86_UP_APIC is not set
That is new. Any thoughts of which patch might be the culprit?
What are the other config options? What XEN options are set?
>
> on i386:
>
> drivers/built-in.o: In function `xen_callback_vector':
> (.text+0x1dc3cb): undefined reference to `first_system_vector'
> drivers/built-in.o: In function `xen_callback_vector':
> (.text+0x1dc3f5): undefined reference to `first_system_vector'
>
>
> --
> ~Randy
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
next prev parent reply other threads:[~2013-06-26 21:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-26 8:06 linux-next: Tree for Jun 26 Stephen Rothwell
2013-06-26 18:48 ` linux-next: Tree for Jun 26 (xen/x86) Randy Dunlap
2013-06-26 21:25 ` Konrad Rzeszutek Wilk [this message]
2013-06-26 22:40 ` [Xen-devel] " Randy Dunlap
2013-07-01 13:50 ` Is: v3.10 + stable/pvh.8 + randy config = compile error. Was:Re: " Konrad Rzeszutek Wilk
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=20130626212509.GB2810@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=virtualization@lists.linux-foundation.org \
--cc=xen-devel@lists.xensource.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).