From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Bastian Blank <bastian@waldi.eu.org>
Cc: xen-devel@lists.xensource.com, "Yu, Ke" <ke.yu@intel.com>
Subject: Re: paravirt-dom0: ACPI_PROCESSOR_XEN (bool) depends on ACPI_PROCESSOR (tristate)
Date: Thu, 08 Oct 2009 11:27:31 -0700 [thread overview]
Message-ID: <4ACE2F13.3020907@goop.org> (raw)
In-Reply-To: <20091008152554.GA12648@wavehammer.waldi.eu.org>
On 10/08/09 08:25, Bastian Blank wrote:
> Haven't you been asked to _NOT_ do such xen-only changes to core
> subsystem code by several people? Somehow I begin to understand why they
> tend to ignore you.
>
Sigh. These patches have not been submitted to upstream, and definitely
need to be refined before I would consider upstreaming them. But the
purpose of this branch is to accumulate all the work people have been
doing as it currently stands, to provide the most functionality for Xen
users.
Ke Yu is the maintainer of this code, and he's aware of this config
dependency problem. I'm looking forward to an appropriate fix from him.
J
prev parent reply other threads:[~2009-10-08 18:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 2:16 paravirt-dom0: ACPI_PROCESSOR_XEN (bool) depends on ACPI_PROCESSOR (tristate) Bastian Blank
2009-10-08 15:25 ` Bastian Blank
2009-10-08 18:27 ` Jeremy Fitzhardinge [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=4ACE2F13.3020907@goop.org \
--to=jeremy@goop.org \
--cc=bastian@waldi.eu.org \
--cc=ke.yu@intel.com \
--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.