public inbox for kvm-ppc@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Alexander Graf <agraf@suse.de>
Cc: "Avi Kivity" <avi@redhat.com>,
	"Anthony Liguori" <anthony@codemonkey.ws>,
	"Andreas Färber" <afaerber@suse.de>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"Marcelo Tosatti" <mtosatti@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"kvm-ppc@vger.kernel.org" <kvm-ppc@vger.kernel.org>
Subject: Re: [Qemu-devel] [PULL 00/20 1.2] kvm updates
Date: Tue, 05 Jun 2012 08:32:37 +0000	[thread overview]
Message-ID: <4FCDC425.4010609@siemens.com> (raw)
In-Reply-To: <74F64445-779D-4F48-B043-0AB8F2E55B26@suse.de>

On 2012-06-05 10:10, Alexander Graf wrote:
> 
> 
> On 05.06.2012, at 09:42, Avi Kivity <avi@redhat.com> wrote:
> 
>> On 06/05/2012 04:58 AM, Anthony Liguori wrote:
>>> On 06/05/2012 08:52 AM, Andreas Färber wrote:
>>>> Am 04.06.2012 07:46, schrieb Anthony Liguori:
>>>>> On 05/22/2012 12:37 AM, Avi Kivity wrote:
>>>>>> Please pull from:
>>>>>>
>>>>>>    git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git uq/master
>>>>>
>>>>> Pulled.  Thanks.
>>>>
>>>> This broke the ppc build. Guys, why wasn't this tested? There's only
>>>> three KVM targets to test compared to the 14 I'm struggling with...
>>>
>>> Is build bot running against uq/master?  If it's not, maybe we should
>>> add it to build bot to catch this sort of thing.
>>
>> A build bot is overkill.  I usually do a full build (and autotest),
>> don't know how this was missed.
> 
> Not sure why it would be overkill. We have build bots running on more exotic hw (ppc and s390) with kvm available for that exact purpose. They're running either way - all we need to do is enable uq/master and we catch these before the next pull request :).

I think this makes some sense. uq/master is supposed to be the staging
branch for generic and (at least) x86 kvm changes in QEMU. So it should
cover at least their builds.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  reply	other threads:[~2012-06-05  8:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1337618267-16669-1-git-send-email-avi@redhat.com>
     [not found] ` <4FCC4BA8.7050900@codemonkey.ws>
2012-06-05  0:52   ` [Qemu-devel] [PULL 00/20 1.2] kvm updates Andreas Färber
2012-06-05  1:58     ` Anthony Liguori
2012-06-05  2:26       ` Andreas Färber
2012-06-05  7:42       ` Avi Kivity
2012-06-05  8:10         ` Alexander Graf
2012-06-05  8:32           ` Jan Kiszka [this message]
2012-06-05  9:02         ` Anthony Liguori
2012-06-05  9:11           ` Avi Kivity

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=4FCDC425.4010609@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox