All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerone Young <jyoung5@us.ibm.com>
To: kvm-ppc@vger.kernel.org
Subject: Re: [kvm-ppc-devel] [PATCH 3 of 4] [qemu ppc uic] Remember
Date: Fri, 28 Mar 2008 04:34:24 +0000	[thread overview]
Message-ID: <1206678864.6752.3.camel@thinkpadL> (raw)
In-Reply-To: <1206676839.6752.1.camel@thinkpadL>

Ah. I've been using Anthony's patch to fix that in my local repo. Yes
will have to push that more kvm-devel so it can be included into the
main tree and we can get around the pit breakage.

On Thu, 2008-03-27 at 23:24 -0500, Hollis Blanchard wrote:
> On Thu, 2008-03-27 at 23:00 -0500, Jerone Young wrote:
> > 
> > > diff --git a/qemu/hw/i8254.c b/qemu/hw/i8254.c
> > > --- a/qemu/hw/i8254.c
> > > +++ b/qemu/hw/i8254.c
> > > @@ -27,6 +27,8 @@
> > >  #include "qemu-timer.h"
> > > 
> > >  #include "qemu-kvm.h"
> > > +
> > > +#undef KVM_CAP_PIT
> > 
> > Did you mean to keep this in your patch? This file is used by i386
> > which does have KVM_CAP_PIT. Did you want to ifdef this ?
> 
> Nope, I forgot about that; thanks for catching it.
> 
> That's just a hack we need to build, since without it our userspace tree
> is broken right now.
> 


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
kvm-ppc-devel mailing list
kvm-ppc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-ppc-devel

      parent reply	other threads:[~2008-03-28  4:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-28  4:00 [kvm-ppc-devel] [PATCH 3 of 4] [qemu ppc uic] Remember Jerone Young
2008-03-28  4:24 ` Hollis Blanchard
2008-03-28  4:34 ` Jerone Young [this message]

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=1206678864.6752.3.camel@thinkpadL \
    --to=jyoung5@us.ibm.com \
    --cc=kvm-ppc@vger.kernel.org \
    /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.