From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Subject: [PULL 0/4] NBD patches through 2020-05-04
Date: Mon, 4 May 2020 16:14:34 -0500 [thread overview]
Message-ID: <20200504211438.195926-1-eblake@redhat.com> (raw)
Happy Star Wars Day! May the Fourth be with you as you apply this...
The following changes since commit 5375af3cd7b8adcc10c18d8083b7be63976c9645:
Merge remote-tracking branch 'remotes/mst/tags/for_upstream' into staging (2020-05-04 15:51:09 +0100)
are available in the Git repository at:
https://repo.or.cz/qemu/ericb.git tags/pull-nbd-2020-05-04
for you to fetch changes up to 714eb0dbc5480c8a9d9f39eb931cb5d2acc1b6c6:
block/nbd-client: drop max_block restriction from discard (2020-05-04 15:16:46 -0500)
----------------------------------------------------------------
nbd patches for 2020-05-04
- reduce client-side fragmentation of NBD trim and status requests
- fix iotest 41 when run in deep tree
- fix socket activation in qemu-nbd
----------------------------------------------------------------
Eric Blake (1):
tools: Fix use of fcntl(F_SETFD) during socket activation
Max Reitz (1):
iotests/041: Fix NBD socket path
Vladimir Sementsov-Ogievskiy (2):
block/nbd-client: drop max_block restriction from block_status
block/nbd-client: drop max_block restriction from discard
block/nbd.c | 6 ++----
util/systemd.c | 4 +++-
tests/qemu-iotests/041 | 2 +-
3 files changed, 6 insertions(+), 6 deletions(-)
--
2.26.2
next reply other threads:[~2020-05-04 21:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 21:14 Eric Blake [this message]
2020-05-04 21:14 ` [PULL 1/4] tools: Fix use of fcntl(F_SETFD) during socket activation Eric Blake
2020-05-04 21:14 ` [PULL 2/4] iotests/041: Fix NBD socket path Eric Blake
2020-05-04 21:14 ` [PULL 3/4] block/nbd-client: drop max_block restriction from block_status Eric Blake
2020-05-04 21:14 ` [PULL 4/4] block/nbd-client: drop max_block restriction from discard Eric Blake
2020-05-05 15:46 ` [PULL 0/4] NBD patches through 2020-05-04 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=20200504211438.195926-1-eblake@redhat.com \
--to=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).