From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org
Cc: xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
David Vrabel <david.vrabel@citrix.com>,
Juergen Gross <jgross@suse.com>
Subject: Re: [Xen-devel] linux-next: Tree for Oct 18 (xen)
Date: Tue, 18 Oct 2016 11:05:37 -0400 [thread overview]
Message-ID: <8924999b-4e51-87e3-5f38-956f53b6da30@oracle.com> (raw)
In-Reply-To: <b6d2f34c-2c5d-32b5-fe81-b7f35606eeb4@infradead.org>
This has already been reported:
http://marc.info/?l=linux-kernel&m=147628583512117&w=3
Thanks.
-boris
On 10/18/2016 10:56 AM, Randy Dunlap wrote:
> On 10/17/16 19:27, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20161017:
>
> on i386:
>
> arch/x86/built-in.o: In function `xen_start_kernel':
> (.init.text+0x2fa6): undefined reference to `xen_cpu_dead'
> arch/x86/built-in.o: In function `xen_start_kernel':
> (.init.text+0x2fab): undefined reference to `xen_cpu_up_prepare'
> arch/x86/built-in.o: In function `xen_start_kernel':
> (.init.text+0x2fc7): undefined reference to `xen_cpu_up_online'
>
>
> Full randconfig file is attached.
>
>
> Reported-by: Randy Dunlap <rdunlap@infradead.org>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> https://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-10-18 15:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 2:27 linux-next: Tree for Oct 18 Stephen Rothwell
2016-10-18 14:56 ` linux-next: Tree for Oct 18 (xen) Randy Dunlap
2016-10-18 15:05 ` Boris Ostrovsky [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=8924999b-4e51-87e3-5f38-956f53b6da30@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).