From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] compile error when CONFIG_XEN_DOM0=n && CONFIG_XEN=y
Date: Wed, 28 Jul 2010 09:23:04 -0400 [thread overview]
Message-ID: <20100728132304.GA4272@phenom.dumpdata.com> (raw)
In-Reply-To: <4C4FCE2F.9000505@goop.org>
On Tue, Jul 27, 2010 at 11:29:03PM -0700, Jeremy Fitzhardinge wrote:
> On 07/27/2010 11:01 AM, Konrad Rzeszutek Wilk wrote:
> >This fixes the mentioned compile error.
> >
> >Please push it in xen/stable-2.6.32.x
>
> Is this detritus from merging, or should it live on a specific topic branch?
Merging. We also have (thanks Ian for spotting this) a
CONFIG_XEN_PCI_PASSTHROUGH that must be enabled to toggle
CONFIG_XEN_PCIDEV_FRONTEND - which is not in my latest upstream trees.
Not sure if it makes sense to drop that or what not - it looks to be
some long forgotten experiment (probably mine) that was not worth the
effort.
prev parent reply other threads:[~2010-07-28 13:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 18:01 [PATCH] compile error when CONFIG_XEN_DOM0=n && CONFIG_XEN=y Konrad Rzeszutek Wilk
2010-07-28 6:29 ` Jeremy Fitzhardinge
2010-07-28 13:23 ` Konrad Rzeszutek Wilk [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=20100728132304.GA4272@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=jeremy@goop.org \
--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.