Re: SOLVED: Re: [Xen-devel] Issue with pv_ops Kernel 2.6.31.6 and Xen [yinghai@xxxxxxxxxx: [PATCH 01/35] x86: fix sci on ioapic 1]

[M A Young <m.a.young@xxxxxxxxxxxx>]

On Wed, 17 Feb 2010, Jeremy Fitzhardinge wrote:

> On 02/17/2010 02:35 PM, M A Young wrote:
> > On Wed, 17 Feb 2010, Jeremy Fitzhardinge wrote:
> >
> > > On 02/17/2010 03:56 AM, M A Young wrote:
> > > > I wouldn't recommend it yet. I have been trying it, but I haven't yet got 
> > > > it to boot, and my most recent attempt a couple of days ago didn't even 
> > > > build (the errors were
> > > > drivers/xen/xenbus/xenbus_probe.c: In function 
> > > > 'exists_connecting_device':
> > > > drivers/xen/xenbus/xenbus_probe.c:791: error: 'xenbus_frontend' 
> > > > undeclared (first use in this function)
> > > > drivers/xen/xenbus/xenbus_probe.c:791: error: (Each undeclared identifier 
> > > > is reported only once
> > > > drivers/xen/xenbus/xenbus_probe.c:791: error: for each function it 
> > > > appears in.)
> > > > drivers/xen/xenbus/xenbus_probe.c: In function 'wait_for_devices':
> > > > drivers/xen/xenbus/xenbus_probe.c:863: error: 'xenbus_frontend' 
> > > > undeclared (first use in this function)
> > > > make[3]: *** [drivers/xen/xenbus/xenbus_probe.o] Error 1
> > > I've fixed that since then.  It really is a WIP is branch.
> > Are you sure? I have just tried a fresh build and it fails in exactly the 
> > same place.
> This is on xen/next, change 507288f2bf47dc2b2aed08c7a9c72c7c1dad8bb4?
I thought it was. However having checked my generation process, it 
turns out that the offending lines had crept back in during my attempts to 
resolve conflicts produced by merging in v2.6.32.8 in git.
        Michael Young

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel