From: Hanna Reitz <hreitz@redhat.com>
To: qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
Hanna Reitz <hreitz@redhat.com>,
qemu-devel@nongnu.org
Subject: [PULL 0/4] Block patches for 7.0-rc2
Date: Tue, 29 Mar 2022 16:58:45 +0200 [thread overview]
Message-ID: <20220329145849.121051-1-hreitz@redhat.com> (raw)
The following changes since commit 44064550d98a680e2ff55fdd783ac19d850ac8ca:
Merge tag 'darwin-20220329' of https://github.com/philmd/qemu into staging (2022-03-29 15:17:53 +0100)
are available in the Git repository at:
https://gitlab.com/hreitz/qemu.git tags/pull-block-2022-03-29
for you to fetch changes up to d5699c0d4b29e919b87049d948a30527897b7e8a:
iotests: Fix status checks (2022-03-29 16:30:55 +0200)
----------------------------------------------------------------
Block patches for 7.0-rc2:
- Disable GLOBAL_STATE_CODE() assertion for the 7.0 release: We got
another bug report for this, and we do not have the time to
investigate before 7.0, so disable the assertion for the release, to
re-enable and continue investigation in the 7.1 cycle
- stream job fix (regarding interaction with concurrent block jobs)
- iotests fixes
----------------------------------------------------------------
Hanna Reitz (3):
main-loop: Disable GLOBAL_STATE_CODE() assertions
block/stream: Drain subtree around graph change
iotests: Fix status checks
John Snow (1):
iotests: update test owner contact information
include/qemu/main-loop.h | 3 ++-
block/stream.c | 15 ++++++++++++++-
tests/qemu-iotests/025 | 2 +-
tests/qemu-iotests/027 | 2 +-
tests/qemu-iotests/028 | 2 +-
tests/qemu-iotests/030 | 30 +++++++++++++++++++++++++-----
tests/qemu-iotests/036 | 2 +-
tests/qemu-iotests/039 | 2 +-
tests/qemu-iotests/041 | 26 +++++++++++++++++++-------
tests/qemu-iotests/059 | 2 +-
tests/qemu-iotests/060 | 2 +-
tests/qemu-iotests/061 | 2 +-
tests/qemu-iotests/062 | 2 +-
tests/qemu-iotests/064 | 2 +-
tests/qemu-iotests/066 | 2 +-
tests/qemu-iotests/068 | 2 +-
tests/qemu-iotests/069 | 2 +-
tests/qemu-iotests/070 | 2 +-
tests/qemu-iotests/071 | 2 +-
tests/qemu-iotests/072 | 2 +-
tests/qemu-iotests/074 | 2 +-
tests/qemu-iotests/084 | 2 +-
tests/qemu-iotests/085 | 2 +-
tests/qemu-iotests/089 | 2 +-
tests/qemu-iotests/090 | 2 +-
tests/qemu-iotests/091 | 2 +-
tests/qemu-iotests/094 | 2 +-
tests/qemu-iotests/095 | 2 +-
tests/qemu-iotests/097 | 2 +-
tests/qemu-iotests/098 | 2 +-
tests/qemu-iotests/099 | 2 +-
tests/qemu-iotests/102 | 2 +-
tests/qemu-iotests/103 | 2 +-
tests/qemu-iotests/105 | 2 +-
tests/qemu-iotests/106 | 2 +-
tests/qemu-iotests/107 | 2 +-
tests/qemu-iotests/108 | 2 +-
tests/qemu-iotests/110 | 2 +-
tests/qemu-iotests/111 | 2 +-
tests/qemu-iotests/112 | 2 +-
tests/qemu-iotests/113 | 2 +-
tests/qemu-iotests/115 | 2 +-
tests/qemu-iotests/117 | 2 +-
tests/qemu-iotests/119 | 2 +-
tests/qemu-iotests/120 | 2 +-
tests/qemu-iotests/121 | 2 +-
tests/qemu-iotests/123 | 2 +-
tests/qemu-iotests/125 | 2 +-
tests/qemu-iotests/126 | 2 +-
tests/qemu-iotests/127 | 2 +-
tests/qemu-iotests/135 | 2 +-
tests/qemu-iotests/138 | 2 +-
tests/qemu-iotests/140 | 2 +-
tests/qemu-iotests/141 | 2 +-
tests/qemu-iotests/143 | 2 +-
tests/qemu-iotests/144 | 2 +-
tests/qemu-iotests/146 | 2 +-
tests/qemu-iotests/150 | 2 +-
tests/qemu-iotests/153 | 2 +-
tests/qemu-iotests/156 | 2 +-
tests/qemu-iotests/162 | 2 +-
tests/qemu-iotests/173 | 2 +-
tests/qemu-iotests/176 | 2 +-
tests/qemu-iotests/182 | 2 +-
tests/qemu-iotests/192 | 2 +-
tests/qemu-iotests/200 | 2 +-
tests/qemu-iotests/216 | 2 +-
tests/qemu-iotests/218 | 2 +-
tests/qemu-iotests/224 | 2 +-
tests/qemu-iotests/225 | 2 +-
tests/qemu-iotests/228 | 2 +-
tests/qemu-iotests/229 | 2 +-
tests/qemu-iotests/231 | 2 +-
tests/qemu-iotests/250 | 2 +-
tests/qemu-iotests/251 | 2 +-
tests/qemu-iotests/252 | 2 +-
tests/qemu-iotests/258 | 2 +-
tests/qemu-iotests/259 | 2 +-
tests/qemu-iotests/261 | 2 +-
tests/qemu-iotests/310 | 2 +-
80 files changed, 136 insertions(+), 90 deletions(-)
--
2.35.1
next reply other threads:[~2022-03-29 15:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 14:58 Hanna Reitz [this message]
2022-03-29 14:58 ` [PULL 1/4] iotests: update test owner contact information Hanna Reitz
2022-03-29 14:58 ` [PULL 2/4] main-loop: Disable GLOBAL_STATE_CODE() assertions Hanna Reitz
2022-03-29 14:58 ` [PULL 3/4] block/stream: Drain subtree around graph change Hanna Reitz
2022-03-29 14:58 ` [PULL 4/4] iotests: Fix status checks Hanna Reitz
2022-03-29 21:20 ` [PULL 0/4] Block patches for 7.0-rc2 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=20220329145849.121051-1-hreitz@redhat.com \
--to=hreitz@redhat.com \
--cc=kwolf@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).