All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alexander Graf <agraf@suse.de>
Cc: Avi Kivity <avi@redhat.com>, KVM list <kvm@vger.kernel.org>
Subject: Re: buildbot failure in kvm on ppc64
Date: Mon, 25 Jun 2012 21:43:03 +1000	[thread overview]
Message-ID: <1340624583.16104.148.camel@pasglop> (raw)
In-Reply-To: <F9CB584D-528D-4AB8-A4C0-2D5EEA3F0DE7@suse.de>

On Mon, 2012-06-25 at 13:03 +0200, Alexander Graf wrote:
> On 25.06.2012, at 11:07, Avi Kivity wrote:
> 
> > On 06/25/2012 09:33 AM, kvm@buildbot.b1-systems.de wrote:
> >> The Buildbot has detected a new failure on builder ppc64 while building kvm.
> >> Full details are available at:
> >> http://buildbot.b1-systems.de/kvm/builders/ppc64/builds/582
> >> 
> >> Buildbot URL: http://buildbot.b1-systems.de/kvm/
> >> 
> >> Buildslave for this Build: b1_kvm_1
> >> 
> >> Build Reason: The Nightly scheduler named 'nightly_master' triggered this build
> >> Build Source Stamp: [branch master] HEAD
> >> Blamelist: 
> >> 
> >> BUILD FAILED: failed compile
> >> 
> > 
> > Alex, did we trigger this somehow?
> 
> I highly doubt it :). Ben, have you seen this before?

Yes, bogus patch from Paul Mundt, the fix is already upstream.

Due to some issues with asm guarding in asm-generic/bug.h

Cheers,
Ben.



  reply	other threads:[~2012-06-25 11:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-25  6:33 buildbot failure in kvm on ppc64 kvm
2012-06-25  9:07 ` Avi Kivity
2012-06-25 11:03   ` Alexander Graf
2012-06-25 11:43     ` Benjamin Herrenschmidt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-04-04  3:56 kvm
2013-02-28  4:05 kvm
2012-03-13  4:21 kvm
2011-09-08  3:03 kvm
2011-07-13  3:17 kvm
2011-05-07  3:06 kvm
2011-02-07  2:30 kvm
2010-12-05  2:10 kvm

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=1340624583.16104.148.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=agraf@suse.de \
    --cc=avi@redhat.com \
    --cc=kvm@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.