All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Knorr <kraxel@suse.de>
To: xen-devel <xen-devel@lists.xensource.com>,
	Ian Pratt <ian.pratt@cl.cam.ac.uk>
Cc: Andi Kleen <ak@suse.de>, Jan Beulich <JBeulich@novell.com>,
	Kurt Garloff <garloff@suse.de>
Subject: merge tree state?
Date: Mon, 05 Dec 2005 18:22:43 +0100	[thread overview]
Message-ID: <43947763.3000007@suse.de> (raw)

   Hi,

What is the current state of the merge tree 
(http://xenbits.xensource.com/ext/linux-2.6-merge.hg)?

I see it gets updates from time to time, but it seems to be out of sync 
nevertheless.  Building it as-is results in a kernel which doesn't boot 
(dom0), both x86_64 and i386, with a 3.0.0 hypervisor kernel.  Further 
inspecition shows that include/arch-xen/xen-public isn't up-to-date. 
Trying to fix that by copying over the latest include files from the 
unstable repository results in build failures in the xen device drivers, 
so these obviously out-of-sync as well ...

cheers,

    Gerd

                 reply	other threads:[~2005-12-05 17:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=43947763.3000007@suse.de \
    --to=kraxel@suse.de \
    --cc=JBeulich@novell.com \
    --cc=ak@suse.de \
    --cc=garloff@suse.de \
    --cc=ian.pratt@cl.cam.ac.uk \
    --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.