From: Thomas Huth <thuth@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>, Max Reitz <mreitz@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Qemu-block <qemu-block@nongnu.org>
Subject: Re: [PULL 0/3] Block patches for 5.1
Date: Tue, 28 Jul 2020 18:22:51 +0200 [thread overview]
Message-ID: <355c94af-aa03-f56f-ee84-e82ef31e797c@redhat.com> (raw)
In-Reply-To: <CAFEAcA_W+G_5iSGj+rg0dx0rUod7XYmR8cxEfGcSKsccVNrtTA@mail.gmail.com>
On 28/07/2020 18.12, Peter Maydell wrote:
> On Tue, 28 Jul 2020 at 11:19, Peter Maydell <peter.maydell@linaro.org> wrote:
>>
>> On Mon, 27 Jul 2020 at 15:38, Max Reitz <mreitz@redhat.com> wrote:
>>> ----------------------------------------------------------------
>>> Block patches for 5.1:
>>> - Coverity fix
>>> - iotests fix for rx and avr
>>> - iotests fix for qcow2 -o compat=0.10
>>>
>>
>> Applied, thanks.
>
> This seems to have broken the "tcg disabled" build on gitlab:
> https://gitlab.com/qemu-project/qemu/-/jobs/659352096
Max already sent another pull request that contains the fix for this
issue, look for "[PULL 0/3] Block patches for 5.1.0-rc2?"
Thomas
next prev parent reply other threads:[~2020-07-28 16:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 14:38 [PULL 0/3] Block patches for 5.1 Max Reitz
2020-07-27 14:38 ` [PULL 1/3] block/amend: Check whether the node exists Max Reitz
2020-07-27 14:38 ` [PULL 2/3] iotests: Select a default machine for the rx and avr targets Max Reitz
2020-07-27 14:38 ` [PULL 3/3] iotests/197: Fix for compat=0.10 Max Reitz
2020-07-28 10:19 ` [PULL 0/3] Block patches for 5.1 Peter Maydell
2020-07-28 16:12 ` Peter Maydell
2020-07-28 16:22 ` Thomas Huth [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-07-21 11:49 Max Reitz
2020-07-21 15:10 ` 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=355c94af-aa03-f56f-ee84-e82ef31e797c@redhat.com \
--to=thuth@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@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).