From: Stefan Hajnoczi <stefanha@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PULL 0/6] NBD patches through 2025-05-29
Date: Sat, 31 May 2025 19:05:36 -0400 [thread overview]
Message-ID: <20250531230536.GA268126@fedora> (raw)
In-Reply-To: <20250529220228.1187563-8-eblake@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 116 bytes --]
Applied, thanks.
Please update the changelog at https://wiki.qemu.org/ChangeLog/10.1 for any user-visible changes.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2025-06-02 11:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-29 22:02 [PULL 0/6] NBD patches through 2025-05-29 Eric Blake
2025-05-29 22:02 ` [PULL 1/6] io: Add helper for setting socket send buffer size Eric Blake
2025-05-29 22:02 ` [PULL 2/6] nbd: Set unix socket send buffer on macOS Eric Blake
2025-05-29 22:02 ` [PULL 3/6] nbd: Set unix socket send buffer on Linux Eric Blake
2025-05-29 22:02 ` [PULL 4/6] iotests: Use disk_usage in more places Eric Blake
2025-05-29 22:02 ` [PULL 5/6] iotests: Improve mirror-sparse on ext4 and xfs Eric Blake
2025-05-29 22:02 ` [PULL 6/6] iotests: Filter out ZFS in several tests Eric Blake
2025-05-31 23:05 ` Stefan Hajnoczi [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=20250531230536.GA268126@fedora \
--to=stefanha@redhat.com \
--cc=eblake@redhat.com \
--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).