All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Christophe Saout <christophe@saout.de>
Cc: xen-devel@lists.xensource.com
Subject: Re: Re: NX related build failure in latest pv_ops dom0 hackery tree
Date: Mon, 13 Apr 2009 11:20:14 -0700	[thread overview]
Message-ID: <49E3825E.2020608@goop.org> (raw)
In-Reply-To: <1239555359.12706.4.camel@leto.intern.saout.de>

Christophe Saout wrote:
> Hi Pasi,
>
>   
>>> Latest tree (as of today) doesn't seem to build for me:
>>> [...]
>>>
>>> Known problem? 
>>>       
>> [written by Jeremy Fitzhardine:]
>>
>> Yes, sorry.   I haven't been updating hackery much lately during the 
>> merge window.  When we see what actually got merged next week, I'll be 
>> rebuilding the xen.git branch structure into something a bit cleaner to 
>> go on with.  I think push2/xen/dom0/master is in a workable state.
>>     
>
> In the meantime, you can try to use that tree:
>
> http://git.saout.de/gitweb/?p=linux-dom0-pvops.git;a=summary
>
> It's the latest tip.git merged with one of the push branches from
> Jeremy's git repo and cherry-picked commits from the backend, blkback
> and netback trees plus minor merge conflict and compile problem fixups.
> It seems feature-complete to me, stable and is able to run DomU domains
> without problems.

Thanks Chris.  I should have a tidied set of branches ready later today, 
along with a great pruning.

    J

  parent reply	other threads:[~2009-04-13 18:20 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-04 19:23 NX related build failure in latest pv_ops dom0 hackery tree Pasi Kärkkäinen
2009-04-05  5:25 ` Jeremy Fitzhardinge
2009-04-12 16:55   ` Christophe Saout
2009-04-12 18:57     ` Boris Derzhavets
2009-04-12 20:06       ` Boris Derzhavets
2009-04-12 20:14         ` Christophe Saout
2009-04-13 10:18     ` Pasi Kärkkäinen
2009-04-13 12:08       ` Boris Derzhavets
2009-04-13 13:28       ` Andrew Lyon
2009-04-13 15:34         ` Boris Derzhavets
2009-04-13 18:20     ` Jeremy Fitzhardinge [this message]
2009-04-14 16:53     ` Jeremy Fitzhardinge
2009-04-14 17:11       ` Thomas DuBuisson
2009-04-14 19:58         ` Jeremy Fitzhardinge
2009-04-14 20:30           ` Thomas DuBuisson
2009-04-14 21:03             ` Jeremy Fitzhardinge
2009-04-15  7:01             ` Pasi Kärkkäinen
2009-04-15 16:08               ` Jeremy Fitzhardinge
2009-04-15 16:55                 ` Thomas DuBuisson
2009-04-15 18:36                   ` Thomas DuBuisson
2009-04-14 17:31       ` Boris Derzhavets
2009-04-14 18:00       ` Boris Derzhavets
2009-04-14 21:43       ` Christophe Saout
2009-04-16 13:16       ` Christophe Saout
2009-04-16 16:13         ` Jeremy Fitzhardinge
2009-04-16 16:24           ` Christophe Saout
2009-04-16 16:34             ` Jeremy Fitzhardinge
2009-04-16 16:49               ` Christophe Saout
2009-04-23 12:01               ` Marc - A. Dahlhaus [ Administration | Westermann GmbH ]
2009-04-23 17:06                 ` Jeremy Fitzhardinge
2009-04-16 16:34             ` Jeremy Fitzhardinge
2009-04-16 22:05           ` Christophe Saout
2009-04-16 22:27             ` Jeremy Fitzhardinge
2009-04-16 23:45               ` Christophe Saout
2009-04-16 23:54                 ` Jeremy Fitzhardinge
2009-04-16 23:54                 ` Christophe Saout
2009-04-17  0:03                   ` Jeremy Fitzhardinge
2009-04-17  0:34                     ` Christophe Saout
2009-04-17  0:49                       ` Jeremy Fitzhardinge
2009-04-17 12:17                         ` Christophe Saout
2009-04-17 12:41                         ` Christophe Saout
2009-04-17 13:58                           ` Jeremy Fitzhardinge
2009-04-17  0:03                   ` Mainline kernel dom0 support Valtteri Kiviniemi
2009-04-18 16:44                     ` Thiago Camargo Martins Cordeiro
2009-04-18 17:26                       ` Thiago Camargo Martins Cordeiro
2009-04-18 20:39                       ` Boris Derzhavets
2009-04-19 19:25                         ` M A Young

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=49E3825E.2020608@goop.org \
    --to=jeremy@goop.org \
    --cc=christophe@saout.de \
    --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.