From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Dan Magenheimer <dan.magenheimer@Oracle.Com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Linux kernel summit 2010 topic: "Xen, in or out" (Greg KH)
Date: Wed, 20 Oct 2010 09:59:20 -0700 [thread overview]
Message-ID: <4CBF1FE8.4050204@goop.org> (raw)
In-Reply-To: <f0cecc6d-b95b-417c-82b3-8bbc4273d62f@default>
On 10/18/2010 07:43 PM, Dan Magenheimer wrote:
> Anybody in the Xen devel community going to be present at Kernel
> Summit 2010? (Not me.)
>
> Maybe it's more ominous than it sounds, but I spotted this
> topic ("Xen in or out", speaker Greg KH) in the proposed topic
> list here:
>
> https://lists.linux-foundation.org/pipermail/ksummit-2010-discuss/2010-September/000331.html
We sorted it out. He was mostly looking at the Novell Xen patch set and
wondering what's going on with Xen development (esp dom0). I pointed
out that Novell maintains its own Xen patches which have little to do
with upstream, and explained what our strategy is for getting dom0
upstream. He was happy with that, and has withdrawn the agenda item.
And BTW, I've been invited to the Kernel Summit for the last 5 years or
so to represent Xen's interests, so there's no risk of that kind of
conversation happening without proper representation ;)
J
prev parent reply other threads:[~2010-10-20 16:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 2:43 Linux kernel summit 2010 topic: "Xen, in or out" (Greg KH) Dan Magenheimer
2010-10-19 8:13 ` Pasi Kärkkäinen
2010-10-19 9:19 ` Sander Eikelenboom
2010-10-19 10:09 ` Keir Fraser
2010-10-19 10:23 ` Sander Eikelenboom
2010-10-19 15:26 ` Konrad Rzeszutek Wilk
2010-10-20 16:59 ` 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=4CBF1FE8.4050204@goop.org \
--to=jeremy@goop.org \
--cc=dan.magenheimer@Oracle.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.