From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: "'xen-devel@lists.xensource.com'" <xen-devel@lists.xensource.com>,
echo@echoreply.us, Anthony Wright <anthony@overnetdata.com>
Subject: Re: What is the current state of Dom0 kernel support?
Date: Wed, 08 Jul 2009 17:23:36 -0700 [thread overview]
Message-ID: <4A553888.1090302@goop.org> (raw)
In-Reply-To: <20090708221423.GE24960@edu.joroinen.fi>
On 07/08/09 15:14, Pasi Kärkkäinen wrote:
> On Fri, Jun 26, 2009 at 11:29:30AM -0700, Jeremy Fitzhardinge wrote:
>
>> On 06/26/09 11:21, Tim Post wrote:
>>
>>> Is it possible for you to set up a blog just for this? I think many
>>> people are just going to pull your tree, it would be really, really nice
>>> to have a feed to pull so we know when to pull and update .. especially
>>> when the next merge window closes.
>>>
>>> As if you didn't have your hands full already :) Perhaps something on
>>> xen.org just for kernel development?
>>>
>>> Sorry if something like this already exists.
>>>
>>>
>> No, its a good idea. I'll sort something out (and poke me if I don't
>> appear to do anything in the next few days).
>>
>>
>
> Btw what's the current tree people should be testing? xen-tip/next or
> rebase/master?
rebase/master is what I'm currently working on. It's work-in-progress,
but it works for me at the moment. I'd appreciate any test results you
have. (I don't yet have a fix in there for your PAE issue however.)
I'm planning on renaming these branches to xen/... and proposing they
become the basis for ongoing work.
J
next prev parent reply other threads:[~2009-07-09 0:23 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 9:32 Xen Source Code Overview Document Stephen Spector
2009-06-18 22:35 ` What is the current state of Dom0 kernel support? Anthony Wright
2009-06-22 4:48 ` Thiago Camargo Martins Cordeiro
2009-06-22 9:21 ` Dennis Krul
2009-06-26 18:04 ` Jeremy Fitzhardinge
2009-06-26 18:21 ` Tim Post
2009-06-26 18:29 ` Jeremy Fitzhardinge
2009-07-08 22:14 ` Pasi Kärkkäinen
2009-07-09 0:23 ` Jeremy Fitzhardinge [this message]
2009-07-09 8:58 ` M A Young
2009-07-09 22:24 ` Pasi Kärkkäinen
2009-07-15 8:22 ` Pasi Kärkkäinen
2009-07-21 13:03 ` What is the current state of Dom0 kernel support? / crash Pasi Kärkkäinen
2009-07-22 19:14 ` Jeremy Fitzhardinge
2009-07-22 19:35 ` Pasi Kärkkäinen
2009-07-22 19:55 ` Jeremy Fitzhardinge
2009-07-22 19:58 ` Pasi Kärkkäinen
2009-07-22 19:57 ` Pasi Kärkkäinen
2009-07-22 20:25 ` Jeremy Fitzhardinge
2009-07-22 20:53 ` Pasi Kärkkäinen
2009-07-29 20:48 ` Jeremy Fitzhardinge
2009-07-30 8:48 ` Pasi Kärkkäinen
2009-07-30 11:35 ` Pasi Kärkkäinen
2009-08-10 16:43 ` Pasi Kärkkäinen
2009-08-10 16:52 ` Jeremy Fitzhardinge
2009-08-10 19:27 ` Pasi Kärkkäinen
2009-08-11 19:58 ` What is the current state of Dom0 kernel support? / crash with 2.6.31-rc5 32bit PAE Pasi Kärkkäinen
2009-08-11 20:12 ` Jeremy Fitzhardinge
2009-08-13 20:17 ` Jeremy Fitzhardinge
2009-08-14 14:15 ` Pasi Kärkkäinen
2009-08-17 15:04 ` What is the current state of Dom0 kernel support? / 2.6.31-rc5 32bit PAE works now! Pasi Kärkkäinen
2009-08-17 15:26 ` Pasi Kärkkäinen
2009-08-17 17:51 ` Jeremy Fitzhardinge
2009-07-23 8:22 ` What is the current state of Dom0 kernel support? Anthony Wright
2009-07-23 8:31 ` Pasi Kärkkäinen
2009-07-23 8:37 ` Keir Fraser
2009-07-24 2:55 ` Simon Horman
2009-07-09 10:11 ` Xen Source Code Overview Document Zhigang Wang
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=4A553888.1090302@goop.org \
--to=jeremy@goop.org \
--cc=anthony@overnetdata.com \
--cc=echo@echoreply.us \
--cc=pasik@iki.fi \
--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.