From: Fam Zheng <famz@redhat.com>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: qemu-devel@nongnu.org, atar4qemu@gmail.com
Subject: Re: [Qemu-devel] [PATCH 0/3] sun4u: move fw_cfg/NVRAM devices to ebus PCI IO address space
Date: Mon, 12 Jun 2017 09:29:07 +0800 [thread overview]
Message-ID: <20170612012907.GA14733@lemon.lan> (raw)
In-Reply-To: <ec44cfad-92a4-664a-4c05-39941bc31480@ilande.co.uk>
On Sat, 06/10 14:31, Mark Cave-Ayland wrote:
> On 10/06/17 14:27, no-reply@patchew.org wrote:
>
> > Hi,
> >
> > This series failed build test on s390x host. Please find the details below.
>
> Well given that it's dependent upon the fw_cfg patchset I posted
> earlier, it's probably going to fail on all hosts :)
>
> Is there a way to express patch dependencies for the patchew builds that
> I'm not aware of?
There currently isn't one but it's being worked on. I will announce it on
qemu-devel@nongnu.org once it's ready. Thanks!
Fam
prev parent reply other threads:[~2017-06-12 1:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-10 13:00 [Qemu-devel] [PATCH 0/3] sun4u: move fw_cfg/NVRAM devices to ebus PCI IO address space Mark Cave-Ayland
2017-06-10 13:00 ` [Qemu-devel] [PATCH 1/3] sun4u: switch to using qdev to instantiate fw_cfg interface Mark Cave-Ayland
2017-06-10 17:55 ` Philippe Mathieu-Daudé
2017-06-11 14:53 ` Mark Cave-Ayland
2017-06-10 13:00 ` [Qemu-devel] [PATCH 2/3] sun4u: expose fw_cfg on ebus PCI IO address space Mark Cave-Ayland
2017-06-10 18:01 ` Philippe Mathieu-Daudé
2017-06-10 13:00 ` [Qemu-devel] [PATCH 3/3] sun4u: expose NVRAM " Mark Cave-Ayland
2017-06-10 18:05 ` Philippe Mathieu-Daudé
2017-06-11 14:58 ` Mark Cave-Ayland
2017-06-12 9:08 ` Artyom Tarasenko
2017-06-10 13:27 ` [Qemu-devel] [PATCH 0/3] sun4u: move fw_cfg/NVRAM devices to " no-reply
2017-06-10 13:31 ` Mark Cave-Ayland
2017-06-12 1:29 ` Fam Zheng [this message]
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=20170612012907.GA14733@lemon.lan \
--to=famz@redhat.com \
--cc=atar4qemu@gmail.com \
--cc=mark.cave-ayland@ilande.co.uk \
--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 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.