qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Subject: [PULL 0/4] NBD patches for soft freeze, 2021-07-09
Date: Fri,  9 Jul 2021 09:09:47 -0500	[thread overview]
Message-ID: <20210709140951.2775730-1-eblake@redhat.com> (raw)

The following changes since commit 9db3065c62a983286d06c207f4981408cf42184d:

  Merge remote-tracking branch 'remotes/vivier2/tags/linux-user-for-6.1-pull-request' into staging (2021-07-08 16:30:18 +0100)

are available in the Git repository at:

  https://repo.or.cz/qemu/ericb.git tags/pull-nbd-2021-07-09

for you to fetch changes up to 62967c9927ec4d733b923c70f9f5428dd1d2e0d7:

  nbd: register yank function earlier (2021-07-09 08:27:33 -0500)

----------------------------------------------------------------
nbd patches for 2021-07-09

- enhance 'qemu-img map --output=json' to make it easier to duplicate
backing chain allocation patterns
- fix a race in the 'yank' QMP command in relation to NBD requests

----------------------------------------------------------------
Eric Blake (3):
      iotests: Improve and rename test 309 to nbd-qemu-allocation
      qemu-img: Make unallocated part of backing chain obvious in map
      qemu-img: Reword 'qemu-img map --output=json' docs

Lukas Straub (1):
      nbd: register yank function earlier

 docs/tools/qemu-img.rst                            |  17 +-
 qapi/block-core.json                               |   7 +-
 block/nbd.c                                        |   8 +-
 qemu-img.c                                         |   7 +-
 tests/qemu-iotests/122.out                         |  84 ++++-----
 tests/qemu-iotests/154.out                         | 190 +++++++++++----------
 tests/qemu-iotests/179.out                         | 133 ++++++++++-----
 tests/qemu-iotests/209.out                         |   4 +-
 tests/qemu-iotests/223.out                         |  56 +++---
 tests/qemu-iotests/244.out                         |  23 +--
 tests/qemu-iotests/252.out                         |  10 +-
 tests/qemu-iotests/274.out                         |  48 +++---
 tests/qemu-iotests/291.out                         |  24 +--
 tests/qemu-iotests/309.out                         |  22 ---
 .../{309 => tests/nbd-qemu-allocation}             |   5 +-
 tests/qemu-iotests/tests/nbd-qemu-allocation.out   |  32 ++++
 16 files changed, 372 insertions(+), 298 deletions(-)
 delete mode 100644 tests/qemu-iotests/309.out
 rename tests/qemu-iotests/{309 => tests/nbd-qemu-allocation} (95%)
 create mode 100644 tests/qemu-iotests/tests/nbd-qemu-allocation.out

-- 
2.31.1



             reply	other threads:[~2021-07-09 14:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-09 14:09 Eric Blake [this message]
2021-07-09 14:09 ` [PULL 1/4] iotests: Improve and rename test 309 to nbd-qemu-allocation Eric Blake
2021-07-09 14:09 ` [PULL 2/4] qemu-img: Make unallocated part of backing chain obvious in map Eric Blake
2021-07-09 14:09 ` [PULL 3/4] qemu-img: Reword 'qemu-img map --output=json' docs Eric Blake
2021-07-09 14:09 ` [PULL 4/4] nbd: register yank function earlier Eric Blake
2021-07-11 12:09 ` [PULL 0/4] NBD patches for soft freeze, 2021-07-09 Peter Maydell
2021-07-12 16:13   ` Eric Blake

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=20210709140951.2775730-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).