From: Kevin Wolf <kwolf@redhat.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, peter.maydell@linaro.org, qemu-devel@nongnu.org
Subject: [PULL 0/3] Block layer patches
Date: Fri, 10 Mar 2023 18:55:26 +0100 [thread overview]
Message-ID: <20230310175529.240379-1-kwolf@redhat.com> (raw)
The following changes since commit ee59483267de29056b5b2ee2421ef3844e5c9932:
Merge tag 'qemu-openbios-20230307' of https://github.com/mcayland/qemu into staging (2023-03-09 16:55:03 +0000)
are available in the Git repository at:
https://repo.or.cz/qemu/kevin.git tags/for-upstream
for you to fetch changes up to ecf8191314798391b1df80bcb829c0ead4f8acc9:
qed: remove spurious BDRV_POLL_WHILE() (2023-03-10 15:14:46 +0100)
----------------------------------------------------------------
Block layer patches
- fuse: Fix fallocate(PUNCH_HOLE) to zero out the range
- qed: remove spurious BDRV_POLL_WHILE()
----------------------------------------------------------------
Hanna Czenczek (2):
block/fuse: Let PUNCH_HOLE write zeroes
iotests/308: Add test for 'write -zu'
Stefan Hajnoczi (1):
qed: remove spurious BDRV_POLL_WHILE()
block/export/fuse.c | 11 ++++++++++-
block/qed.c | 1 -
tests/qemu-iotests/308 | 43 +++++++++++++++++++++++++++++++++++++++++++
tests/qemu-iotests/308.out | 35 +++++++++++++++++++++++++++++++++++
4 files changed, 88 insertions(+), 2 deletions(-)
next reply other threads:[~2023-03-10 17:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 17:55 Kevin Wolf [this message]
2023-03-10 17:55 ` [PULL 1/3] block/fuse: Let PUNCH_HOLE write zeroes Kevin Wolf
2023-03-10 17:55 ` [PULL 2/3] iotests/308: Add test for 'write -zu' Kevin Wolf
2023-03-10 17:55 ` [PULL 3/3] qed: remove spurious BDRV_POLL_WHILE() Kevin Wolf
2023-03-12 17:41 ` [PULL 0/3] Block layer patches Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2022-02-11 17:58 Kevin Wolf
2022-02-14 21:48 ` 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=20230310175529.240379-1-kwolf@redhat.com \
--to=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).