qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
	Eduardo Habkost <ehabkost@redhat.com>,
	"patches@linaro.org" <patches@linaro.org>,
	Laurent Vivier <laurent@vivier.eu>,
	Paolo Bonzini <pbonzini@redhat.com>,
	"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH for-2.9 0/6] disas: Fix various coverity nits
Date: Mon, 6 Mar 2017 09:03:03 +0800	[thread overview]
Message-ID: <20170306010303.GA31251@lemon.lan> (raw)
In-Reply-To: <CAFEAcA-D37hty_DmU-VtudwnrEMeS=93HB5pe4HHL9GThRbQxQ@mail.gmail.com>

On Sat, 03/04 12:44, Peter Maydell wrote:
> On 4 March 2017 at 00:00,  <no-reply@patchew.org> wrote:
> > Hi,
> >
> > This series failed build test on s390x host. Please find the details below.
> 
> > === TEST BEGIN ===
> > Using CC: /home/fam/bin/cc
> > rm: cannot remove '/var/tmp/patchew-qemu-build/aarch64-softmmu': Directory not empty
> > === OUTPUT END ===
> 
> Fam, can we drop the s390x test from patchew until it gets fixed,
> please? Right now it's just spamming the list and means that
> actually interesting patchew emails are likely to get ignored...

OK, I've changed this test to off-list reply and I'll continue investigating.
Though I think that apart from this apparent tester hiccup and another one false
positive out of my manual intervention, other s390x reports are actual QEMU
issue.

Fam

  reply	other threads:[~2017-03-06  1:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-03 15:50 [Qemu-devel] [PATCH for-2.9 0/6] disas: Fix various coverity nits Peter Maydell
2017-03-03 15:50 ` [Qemu-devel] [PATCH for-2.9 1/6] disas/hppa: Remove dead code Peter Maydell
2017-03-03 19:40   ` Philippe Mathieu-Daudé
2017-03-03 15:50 ` [Qemu-devel] [PATCH for-2.9 2/6] disas/i386: Avoid NULL pointer dereference in error case Peter Maydell
2017-03-03 15:50 ` [Qemu-devel] [PATCH for-2.9 3/6] disas/m68k: Avoid unintended sign extension in get_field() Peter Maydell
2017-03-03 18:56   ` Laurent Vivier
2017-03-03 15:50 ` [Qemu-devel] [PATCH for-2.9 4/6] disas/microblaze: Avoid unintended sign extension Peter Maydell
2017-03-03 15:58   ` Edgar E. Iglesias
2017-03-03 16:02     ` Peter Maydell
2017-03-03 16:06       ` Edgar E. Iglesias
2017-03-03 15:50 ` [Qemu-devel] [PATCH for-2.9 5/6] disas/cris: " Peter Maydell
2017-03-03 15:58   ` Edgar E. Iglesias
2017-03-03 19:43     ` Philippe Mathieu-Daudé
2017-03-03 15:50 ` [Qemu-devel] [PATCH for-2.9 6/6] disas/arm: " Peter Maydell
2017-03-03 16:11 ` [Qemu-devel] [PATCH for-2.9 0/6] disas: Fix various coverity nits no-reply
2017-03-04  0:00 ` no-reply
2017-03-04 12:44   ` Peter Maydell
2017-03-06  1:03     ` Fam Zheng [this message]
2017-03-07 17:06 ` Peter Maydell

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=20170306010303.GA31251@lemon.lan \
    --to=famz@redhat.com \
    --cc=edgar.iglesias@gmail.com \
    --cc=ehabkost@redhat.com \
    --cc=laurent@vivier.eu \
    --cc=patches@linaro.org \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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).