qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, peter.maydell@linaro.org, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL v2 00/14] Block layer patches for 2.10.0-rc1
Date: Tue,  1 Aug 2017 18:12:39 +0200	[thread overview]
Message-ID: <20170801161239.9447-1-kwolf@redhat.com> (raw)

The following changes since commit 5619c179057e24195ff19c8fe6d6a6cbcb16ed28:

  Merge remote-tracking branch 'remotes/pmaydell/tags/pull-target-arm-20170731' into staging (2017-07-31 14:45:42 +0100)

are available in the git repository at:

  git://repo.or.cz/qemu/kevin.git tags/for-upstream

for you to fetch changes up to 8e8eb0a9035e5b6c6447c82138570e388282cfa2:

  block/qapi: Remove redundant NULL check to silence Coverity (2017-08-01 18:09:33 +0200)

----------------------------------------------------------------
Block layer patches for 2.10.0-rc1

----------------------------------------------------------------
Eric Blake (2):
      iotests: Check dirty bitmap statistics in 124
      iotests: Add test of recent fix to 'qemu-img measure'

Kevin Wolf (8):
      qemu-iotests/041: Fix leaked scratch images
      qemu-iotests: Remove blkdebug.conf after tests
      qemu-iotests/141: Fix image cleanup
      qemu-iotests/153: Fix leaked scratch images
      qemu-iotests/162: Fix leaked temporary files
      qemu-iotests/063: Fix leaked image
      qemu-iotests/059: Fix leaked image files
      block/qapi: Remove redundant NULL check to silence Coverity

Manos Pitsidianakis (2):
      block: fix dangling bs->explicit_options in block.c
      block: fix leaks in bdrv_open_driver()

Max Reitz (2):
      iotests: Fix test 156
      iotests: Redirect stderr to stdout in 186

 block.c                      | 24 +++++++++---------
 block/qapi.c                 |  3 ++-
 tests/qemu-iotests/041       |  4 ++-
 tests/qemu-iotests/059       | 11 ++++++++-
 tests/qemu-iotests/059.out   | 22 ++++++++---------
 tests/qemu-iotests/063       |  4 +--
 tests/qemu-iotests/074       |  1 +
 tests/qemu-iotests/124       |  7 +++++-
 tests/qemu-iotests/141       |  2 +-
 tests/qemu-iotests/153       |  1 +
 tests/qemu-iotests/156       |  4 +--
 tests/qemu-iotests/162       |  7 ++++++
 tests/qemu-iotests/179       |  1 +
 tests/qemu-iotests/186       |  2 +-
 tests/qemu-iotests/186.out   | 12 ++++-----
 tests/qemu-iotests/190       | 59 ++++++++++++++++++++++++++++++++++++++++++++
 tests/qemu-iotests/190.out   | 11 +++++++++
 tests/qemu-iotests/common.rc |  3 +++
 tests/qemu-iotests/group     |  1 +
 19 files changed, 140 insertions(+), 39 deletions(-)
 create mode 100755 tests/qemu-iotests/190
 create mode 100644 tests/qemu-iotests/190.out

             reply	other threads:[~2017-08-01 16:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-01 16:12 Kevin Wolf [this message]
2017-08-01 17:01 ` [Qemu-devel] [PULL v2 00/14] Block layer patches for 2.10.0-rc1 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=20170801161239.9447-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).