From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Guenter Roeck <linux@roeck-us.net>, qemu-devel@nongnu.org
Cc: andrew@aj.id.au, peter.maydell@linaro.org, qemu-arm@nongnu.org,
clg@kaod.org, joel@jms.id.au
Subject: Re: [PATCH v2] hw/arm: ast2600: Wire up EHCI controllers
Date: Tue, 11 Feb 2020 09:12:07 +0100 [thread overview]
Message-ID: <445cee18-5de3-3da4-fef4-2e3f4530d96b@redhat.com> (raw)
In-Reply-To: <20200207224850.GA10890@roeck-us.net>
On 2/7/20 11:48 PM, Guenter Roeck wrote:
> On Fri, Feb 07, 2020 at 02:04:09PM -0800, no-reply@patchew.org wrote:
>> Patchew URL: https://patchew.org/QEMU/20200207174548.9087-1-linux@roeck-us.net/
>>
>>
>>
>> Hi,
>>
>> This series failed the docker-mingw@fedora build test. Please find the testing commands and
>> their output below. If you have Docker installed, you can probably reproduce it
>> locally.
>>
> I forgot to mention that the patch depends on the similar
> patch for ast2400/ast2500. Sorry for that. Not sure though how
> to tell that to the test build system.
You mean the "Aspeed: machine extensions and fixes" series?
Use the 'based-on' tag with the series cover message-id in your cover/patch:
Based-on: <20190904070506.1052-1-clg@kaod.org>
next prev parent reply other threads:[~2020-02-11 8:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 17:45 [PATCH v2] hw/arm: ast2600: Wire up EHCI controllers Guenter Roeck
2020-02-07 21:25 ` Niek Linnenbank
2020-02-07 21:34 ` Guenter Roeck
2020-02-07 22:15 ` Niek Linnenbank
2020-02-07 22:04 ` no-reply
2020-02-07 22:48 ` Guenter Roeck
2020-02-11 8:12 ` Philippe Mathieu-Daudé [this message]
2020-02-11 19:13 ` Peter Maydell
2020-02-11 19:33 ` Guenter Roeck
2020-02-07 23:23 ` no-reply
2020-02-07 23:25 ` no-reply
2020-02-13 11:58 ` 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=445cee18-5de3-3da4-fef4-2e3f4530d96b@redhat.com \
--to=philmd@redhat.com \
--cc=andrew@aj.id.au \
--cc=clg@kaod.org \
--cc=joel@jms.id.au \
--cc=linux@roeck-us.net \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--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;
as well as URLs for NNTP newsgroup(s).