From: Jeremy Fitzhardinge <jeremy@goop.org>
To: M A Young <m.a.young@durham.ac.uk>
Cc: Marcial Rion <marcial.rion@swissonline.ch>,
xen-devel@lists.xensource.com,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: SOLVED: Re: Issue with pv_ops Kernel 2.6.31.6 and Xen [yinghai@kernel.org: [PATCH 01/35] x86: fix sci on ioapic 1]
Date: Wed, 17 Feb 2010 10:53:27 -0800 [thread overview]
Message-ID: <4B7C3B27.9020506@goop.org> (raw)
In-Reply-To: <alpine.GSO.2.00.1002171151280.2452@algedi.dur.ac.uk>
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.
J
next prev parent reply other threads:[~2010-02-17 18:53 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 15:39 Issue with pv_ops Kernel 2.6.31.6 and Xen [yinghai@kernel.org: [PATCH 01/35] x86: fix sci on ioapic 1] Konrad Rzeszutek Wilk
2010-02-13 23:12 ` Marcial Rion
2010-02-16 18:10 ` SOLVED: " Konrad Rzeszutek Wilk
2010-02-16 21:51 ` Jeremy Fitzhardinge
2010-02-17 8:33 ` Pasi Kärkkäinen
2010-02-17 11:56 ` M A Young
2010-02-17 18:53 ` Jeremy Fitzhardinge [this message]
2010-02-17 22:35 ` M A Young
2010-02-17 22:56 ` Jeremy Fitzhardinge
2010-02-17 23:24 ` M A Young
2010-02-17 18:52 ` Jeremy Fitzhardinge
2010-02-17 19:07 ` Michael D Labriola
2010-02-17 19:20 ` Pasi Kärkkäinen
2010-02-17 19:36 ` Jeremy Fitzhardinge
2010-02-17 19:41 ` Pasi Kärkkäinen
2010-02-17 19:47 ` Michael D Labriola
2010-02-17 19:55 ` Pasi Kärkkäinen
2010-02-17 19:34 ` Jeremy Fitzhardinge
2010-02-20 15:29 ` xen/next Linux 2.6.32 pv_ops dom0 kernel Pasi Kärkkäinen
2010-02-20 19:55 ` Stefan Kuhne
2010-02-20 20:50 ` Boris Derzhavets
2010-02-20 21:01 ` Boris Derzhavets
2010-02-21 2:02 ` Pasi Kärkkäinen
2010-02-23 18:41 ` Martinx
2010-02-23 19:07 ` Boris Derzhavets
2010-02-22 20:27 ` Jeremy Fitzhardinge
2010-02-22 23:23 ` Pasi Kärkkäinen
2010-02-22 23:34 ` Jeremy Fitzhardinge
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=4B7C3B27.9020506@goop.org \
--to=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=m.a.young@durham.ac.uk \
--cc=marcial.rion@swissonline.ch \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.