From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Yu Zhiguo <yuzg@cn.fujitsu.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] pv-ops: Fix missing 'ifdef CONFIG_XEN' in acpi
Date: Fri, 16 Apr 2010 10:56:04 -0400 [thread overview]
Message-ID: <20100416145604.GC29398@phenom.dumpdata.com> (raw)
In-Reply-To: <4BC7C657.3010609@cn.fujitsu.com>
On Fri, Apr 16, 2010 at 10:07:19AM +0800, Yu Zhiguo wrote:
>
> routines 'xen_register_gsi' and 'xen_teardown_msi_dev' cannot be used
> unless macro 'CONFIG_XEN' is defined, otherwise build error occurs.
There has to be a better of doing this. Aren't the
xen_register_gsi defined in the header files? How about making in the
header file the #ifdef CONFIG_XEN there?
next prev parent reply other threads:[~2010-04-16 14:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 2:07 [PATCH] pv-ops: Fix missing 'ifdef CONFIG_XEN' in acpi Yu Zhiguo
2010-04-16 14:56 ` Konrad Rzeszutek Wilk [this message]
2010-04-18 3:56 ` Yu Zhiguo
2010-04-18 4:46 ` Jeremy Fitzhardinge
2010-04-19 13:30 ` Konrad Rzeszutek Wilk
2010-04-19 16:22 ` Jeremy Fitzhardinge
2010-04-20 5:31 ` Yu Zhiguo
2010-04-20 18:33 ` Konrad Rzeszutek Wilk
2010-04-21 3:29 ` Yu Zhiguo
2010-04-21 13:00 ` Konrad Rzeszutek Wilk
2010-04-21 13:53 ` Yu Zhiguo
2010-04-21 16:33 ` Jeremy Fitzhardinge
2010-04-22 4:05 ` Yu Zhiguo
2010-04-22 16:27 ` Jeremy Fitzhardinge
2010-04-25 4:24 ` Yu Zhiguo
2010-04-21 16:31 ` Jeremy Fitzhardinge
2010-04-19 11:23 ` Failure to load the most recent kernel 2.6.10 ( xen/stable) under Xen 4.0 on Ubuntu 9.10 Boris Derzhavets
2010-04-20 10:44 ` Failure to load the most recent kernel 2.6.32.10 " Boris Derzhavets
2010-04-20 12:46 ` Boris Derzhavets
2010-04-20 18:21 ` Jeremy Fitzhardinge
2010-04-20 21:25 ` Boris Derzhavets
2010-04-21 8:05 ` Yu, Ke
2010-04-21 12:19 ` Boris Derzhavets
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=20100416145604.GC29398@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=jeremy@goop.org \
--cc=xen-devel@lists.xensource.com \
--cc=yuzg@cn.fujitsu.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).