qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org, no-reply@patchew.org, f4bug@amsat.org
Cc: peter.maydell@linaro.org, james.hogan@imgtec.com,
	famz@redhat.com, quintela@redhat.com,
	crosthwaite.peter@gmail.com, programmingkidx@gmail.com,
	yongbok.kim@imgtec.com, pbonzini@redhat.com,
	aurelien@aurel32.net
Subject: Re: [Qemu-devel] [PATCH for 2.10 0/4] check dtc submodule is outdated
Date: Wed, 26 Jul 2017 16:56:18 -0500	[thread overview]
Message-ID: <6ccbdea1-be5e-2dbe-d84a-314fc2d6f666@redhat.com> (raw)
In-Reply-To: <150110567183.114.17390976982809714249@5d477a5b5989>

[-- Attachment #1: Type: text/plain, Size: 951 bytes --]

On 07/26/2017 04:47 PM, no-reply@patchew.org wrote:
> Hi,
> 
> This series failed build test on s390x host. Please find the details below.
> 
> Type: series
> Subject: [Qemu-devel] [PATCH for 2.10 0/4] check dtc submodule is outdated
> Message-id: 20170726214010.420-1-f4bug@amsat.org
> 

> === TEST BEGIN ===
> Using CC: /home/fam/bin/cc
> 
> ERROR: fdt disabled but some requested targets require it.
>        You can turn off fdt only if you also disable all the system emulation
>        targets which need it (by specifying a cut down --target-list).

Well, your new configure check certainly fired!  The question is whether
it was supposed to (meaning patchew needs to tweak what it tries to
configure), or whether there's a logic bug in your patch (meaning it
fails when it shouldn't have).

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]

  reply	other threads:[~2017-07-26 21:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-26 21:40 [Qemu-devel] [PATCH for 2.10 0/4] check dtc submodule is outdated Philippe Mathieu-Daudé
2017-07-26 21:40 ` [Qemu-devel] [PATCH 1/4] configure: remember the user to run 'git submodule' command in source dir Philippe Mathieu-Daudé
2017-07-26 21:51   ` Eric Blake
2017-07-26 22:02     ` Philippe Mathieu-Daudé
2017-07-26 21:40 ` [Qemu-devel] [PATCH for 2.10 2/4] fdt: check fdt_required condition can be satisfied _after_ testing libfdt Philippe Mathieu-Daudé
2017-07-26 21:53   ` Eric Blake
2017-07-27 21:46   ` Michael Roth
2017-07-26 21:40 ` [Qemu-devel] [PATCH for 2.10 3/4] fdt: probe for v1.4.2 using fdt_setprop_inplace_namelen_partial() Philippe Mathieu-Daudé
2017-07-27 21:43   ` Michael Roth
2017-07-27 22:45     ` Michael Roth
2017-07-26 21:40 ` [Qemu-devel] [RFC PATCH for 2.10 4/4] fdt: compile dtc submodule to check it is up-to-date Philippe Mathieu-Daudé
2017-07-26 21:47 ` [Qemu-devel] [PATCH for 2.10 0/4] check dtc submodule is outdated no-reply
2017-07-26 21:56   ` Eric Blake [this message]
2017-07-26 22:05     ` Philippe Mathieu-Daudé
2017-07-27  4:39 ` Philippe Mathieu-Daudé

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=6ccbdea1-be5e-2dbe-d84a-314fc2d6f666@redhat.com \
    --to=eblake@redhat.com \
    --cc=aurelien@aurel32.net \
    --cc=crosthwaite.peter@gmail.com \
    --cc=f4bug@amsat.org \
    --cc=famz@redhat.com \
    --cc=james.hogan@imgtec.com \
    --cc=no-reply@patchew.org \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=programmingkidx@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=yongbok.kim@imgtec.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 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).