From: no-reply@patchew.org
To: laurent@vivier.eu
Cc: riku.voipio@iki.fi, qemu-devel@nongnu.org, laurent@vivier.eu
Subject: Re: [Qemu-devel] [PATCH] linux-user: move QEMU_IFLA_BR_MULTI_BOOLOPT to the good function
Date: Wed, 26 Jun 2019 08:15:11 -0700 (PDT) [thread overview]
Message-ID: <156156211053.6332.18156620782204988441@c4a48874b076> (raw)
In-Reply-To: <20190626150855.27446-1-laurent@vivier.eu>
Patchew URL: https://patchew.org/QEMU/20190626150855.27446-1-laurent@vivier.eu/
Hi,
This series failed build test on s390x host. Please find the details below.
The full log is available at
http://patchew.org/logs/20190626150855.27446-1-laurent@vivier.eu/testing.s390x/?type=message.
---
Email generated automatically by Patchew [https://patchew.org/].
Please send your feedback to patchew-devel@redhat.com
next prev parent reply other threads:[~2019-06-26 15:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 15:08 [Qemu-devel] [PATCH] linux-user: move QEMU_IFLA_BR_MULTI_BOOLOPT to the good function Laurent Vivier
2019-06-26 15:15 ` no-reply [this message]
2019-07-01 8:51 ` Laurent Vivier
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=156156211053.6332.18156620782204988441@c4a48874b076 \
--to=no-reply@patchew.org \
--cc=laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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).