From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Xen Devel <Xen-devel@lists.xensource.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the xen tree
Date: Thu, 15 Sep 2011 02:10:46 -0700 [thread overview]
Message-ID: <4E71C116.4080400@goop.org> (raw)
In-Reply-To: <20110915152723.b3bdd6a5478c810245fabca1@canb.auug.org.au>
On 09/14/2011 10:27 PM, Stephen Rothwell wrote:
> Hi all,
>
> After merging the xen tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> arch/x86/xen/time.c: In function 'xen_set_wallclock':
> arch/x86/xen/time.c:204:25: error: storage size of 'op' isn't known
> arch/x86/xen/time.c:211:11: error: 'XENPF_settime' undeclared (first
use in this function)
> arch/x86/xen/time.c:211:11: note: each undeclared identifier is
reported only once for each function it appears in
> arch/x86/xen/time.c:216:2: error: implicit declaration of function
'HYPERVISOR_dom0_op'
> arch/x86/xen/time.c:204:25: warning: unused variable 'op'
>
> Caused by commit 7b11a83f592a ("xen/dom0: set wallclock time in Xen").
>
> I have used teh xen tree from next-20110914 for today.
Thanks, I'll drop that for now.
J
next prev parent reply other threads:[~2011-09-15 9:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 5:27 linux-next: build failure after merge of the xen tree Stephen Rothwell
2011-09-15 9:10 ` Jeremy Fitzhardinge [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-10-27 2:02 Stephen Rothwell
2010-10-25 2:30 Stephen Rothwell
2010-10-25 8:38 ` Ian Campbell
2010-10-25 23:57 ` Jeremy Fitzhardinge
2010-07-28 4:18 Stephen Rothwell
2010-07-23 4:01 Stephen Rothwell
2010-07-23 4:48 ` Jeremy Fitzhardinge
2010-07-23 5:56 ` Jeremy Fitzhardinge
2010-07-23 6:05 ` Jeremy Fitzhardinge
2010-07-23 6:59 ` Stephen Rothwell
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=4E71C116.4080400@goop.org \
--to=jeremy@goop.org \
--cc=Xen-devel@lists.xensource.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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