xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: AP Xen <apxeng@gmail.com>
To: xen-devel@lists.xensource.com
Subject: Re: Building Dom0 for Xen 4.1
Date: Wed, 27 Apr 2011 19:44:36 -0700	[thread overview]
Message-ID: <BANLkTikaPSe2RxT-QtcE2rnwEJZh-ZWwog@mail.gmail.com> (raw)
In-Reply-To: <BANLkTikSypquuCibCU9W822EV_syL+k4UQ@mail.gmail.com>

Sorry I hit send prematurely...

So is the current standard for building a Dom0 kernel the one
described in http://wiki.xen.org/xenwiki/XenParavirtOps?

On Wed, Apr 27, 2011 at 7:42 PM, AP Xen <apxeng@gmail.com> wrote:
> With Xen 4.0.1, when I do a "make world", it pulls down Jeremy's git
> tree and builds it. With Xen 4.1 this no longer happens either with
> "make world" or "make kernels". Is this by design? So is the way to do
> this as l  method as listed in
> http://wiki.xen.org/xenwiki/XenParavirtOps?
>
> Thanks,
> AP
>

  reply	other threads:[~2011-04-28  2:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-28  2:42 Building Dom0 for Xen 4.1 AP Xen
2011-04-28  2:44 ` AP Xen [this message]
2011-04-28  7:32   ` Ian Campbell

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=BANLkTikaPSe2RxT-QtcE2rnwEJZh-ZWwog@mail.gmail.com \
    --to=apxeng@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).