From: Richard Henderson <richard.henderson@linaro.org>
To: Kevin Wolf <kwolf@redhat.com>, qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org
Subject: Re: [PULL v2 00/21] Block layer patches
Date: Fri, 19 May 2023 08:53:15 -0700 [thread overview]
Message-ID: <7230d02b-e9f9-aa1b-3aa8-67aec82494a7@linaro.org> (raw)
In-Reply-To: <20230519105013.217914-1-kwolf@redhat.com>
On 5/19/23 03:50, Kevin Wolf wrote:
> The following changes since commit 6972ef1440a9d685482d78672620a7482f2bd09a:
>
> Merge tag 'pull-tcg-20230516-3' of https://gitlab.com/rth7680/qemu into staging (2023-05-16 21:30:27 -0700)
>
> are available in the Git repository at:
>
> https://repo.or.cz/qemu/kevin.git tags/for-upstream
>
> for you to fetch changes up to c1bc2467c25ae2b846eeb5d338d1c697c6f83833:
>
> iotests: Test commit with iothreads and ongoing I/O (2023-05-19 11:32:19 +0200)
>
> ----------------------------------------------------------------
> Block layer patches
>
> - qcow2 spec: Rename "zlib" compression to "deflate"
> - Honour graph read lock even in the main thread + prerequisite fixes
> - aio-posix: do not nest poll handlers (fixes infinite recursion)
> - Refactor QMP blockdev transactions
> - graph-lock: Disable locking for now
> - iotests/245: Check if 'compress' driver is available
Build failure:
https://gitlab.com/qemu-project/qemu/-/jobs/4316574356#L3199
../block/graph-lock.c: In function ‘assert_bdrv_graph_readable’:
../block/graph-lock.c:278:37: error: implicit declaration of function ‘reader_count’
[-Werror=implicit-function-declaration]
278 | assert(qemu_in_main_thread() || reader_count());
| ^~~~~~~~~~~~
../block/graph-lock.c:278:37: error: nested extern declaration of ‘reader_count’
[-Werror=nested-externs]
r~
prev parent reply other threads:[~2023-05-19 15:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 10:50 [PULL v2 00/21] Block layer patches Kevin Wolf
2023-05-19 15:53 ` Richard Henderson [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=7230d02b-e9f9-aa1b-3aa8-67aec82494a7@linaro.org \
--to=richard.henderson@linaro.org \
--cc=kwolf@redhat.com \
--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).