From: Anthony Wright <anthony@overnetdata.com>
To: xen-devel@lists.xensource.com
Cc: jeremy@goop.org
Subject: Re: xen.git branch reorg - patches for dom0 in 2.6.29 or 2.6.30?
Date: Mon, 27 Apr 2009 15:17:49 +0100 [thread overview]
Message-ID: <49F5BE8D.8040201@overnetdata.com> (raw)
Jeremy Fitzhardinge wrote:
>Pasi Kärkkäinen wrote:
>>Btw how does dom0 upstreaming look at the moment? Ingo sent pull
>>request about some changes, and those got merged, but how about the
>>rest?
>
>Ingo basically ignored all the Xen changes in the leadup to the merge
>window, then stomped on my attempt to get them merged with Linus, which
>was all pretty annoying. It had the doubly-irritating side-effect of
>casting doubt over the controversy-free domU changes, so they didn't
>get merged in the merge window either; by the time Ingo got around to
>OKing them, the window had closed. So all that got merged in the end
>was the must-have bug fixes.
>Linus isn't going to pull any more major functionality changes in the
>-rc kernels, and certainly isn't going to make an exception for Xen. So
>we're stuck with waiting for the .31 merge window.
>
> J
Given that you think it'll be 2.6.31 before the linux kernel contains
dom0 support (which I guess will be released around Sept/Oct '09), will
you do a release of the code so that people like me who *really* want to
have the latest kernel running as dom0 (to get up to date driver
support) can patch their 2.6.29 (or 2.6.30) kernel. Alternatively could
you give some pointers on how to extract it from git and patch the kernel.
thanks,
Anthony Wright.
next reply other threads:[~2009-04-27 14:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 14:17 Anthony Wright [this message]
2009-04-27 17:50 ` xen.git branch reorg - patches for dom0 in 2.6.29 or 2.6.30? 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=49F5BE8D.8040201@overnetdata.com \
--to=anthony@overnetdata.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.