From: Peter Maydell <peter.maydell@linaro.org>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL for-2.11-rc2 0/5] Block patches
Date: Tue, 14 Nov 2017 16:52:49 +0000 [thread overview]
Message-ID: <CAFEAcA_m9JnMVTsAXCf=qHWoJAst9pz=rA9DNCbakYLtkxedSw@mail.gmail.com> (raw)
In-Reply-To: <20171114103721.13869-1-stefanha@redhat.com>
On 14 November 2017 at 10:37, Stefan Hajnoczi <stefanha@redhat.com> wrote:
> The following changes since commit 508ba0f7e2092d3ca56e3f75e894d52d8b94818e:
>
> Merge remote-tracking branch 'remotes/cohuck/tags/s390x-20171109' into staging (2017-11-13 11:41:47 +0000)
>
> are available in the git repository at:
>
> git://github.com/stefanha/qemu.git tags/block-pull-request
>
> for you to fetch changes up to 0761562687e0d8135310a94b1d3e08376387c027:
>
> qemu-iotests: Test I/O limits with removable media (2017-11-13 15:46:26 +0000)
>
> ----------------------------------------------------------------
> Pull request
>
> The following disk I/O throttling fixes solve recent bugs.
Applied, thanks.
-- PMM
prev parent reply other threads:[~2017-11-14 16:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 10:37 [Qemu-devel] [PULL for-2.11-rc2 0/5] Block patches Stefan Hajnoczi
2017-11-14 10:37 ` [Qemu-devel] [PULL for-2.11-rc2 1/5] block: all I/O should be completed before removing throttle timers Stefan Hajnoczi
2017-11-14 10:37 ` [Qemu-devel] [PULL for-2.11-rc2 2/5] throttle-groups: drain before detaching ThrottleState Stefan Hajnoczi
2017-11-14 10:37 ` [Qemu-devel] [PULL for-2.11-rc2 3/5] block: Check for inserted BlockDriverState in blk_io_limits_disable() Stefan Hajnoczi
2017-11-14 10:37 ` [Qemu-devel] [PULL for-2.11-rc2 4/5] block: Leave valid throttle timers when removing a BDS from a backend Stefan Hajnoczi
2017-11-14 10:37 ` [Qemu-devel] [PULL for-2.11-rc2 5/5] qemu-iotests: Test I/O limits with removable media Stefan Hajnoczi
2017-11-14 16:52 ` Peter Maydell [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='CAFEAcA_m9JnMVTsAXCf=qHWoJAst9pz=rA9DNCbakYLtkxedSw@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).