From: Peter Maydell <peter.maydell@linaro.org>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL for-2.4 0/3] Block patches
Date: Wed, 29 Jul 2015 18:49:07 +0100 [thread overview]
Message-ID: <CAFEAcA8P_anW1NbC0FcxzHSCoRXaKgs_OWikuWkprkFXT7DNgw@mail.gmail.com> (raw)
In-Reply-To: <1438177831-28195-1-git-send-email-stefanha@redhat.com>
On 29 July 2015 at 14:50, Stefan Hajnoczi <stefanha@redhat.com> wrote:
> The following changes since commit b83d017d88b2c4710c7a4614ecf9f845e4db80ba:
>
> Merge remote-tracking branch 'remotes/stefanha/tags/net-pull-request' into staging (2015-07-28 19:02:04 +0100)
>
> are available in the git repository at:
>
> git://github.com/stefanha/qemu.git tags/block-pull-request
>
> for you to fetch changes up to ca96ac44dcd290566090b2435bc828fded356ad9:
>
> AioContext: force event loop iteration using BH (2015-07-29 10:02:06 +0100)
>
> ----------------------------------------------------------------
> Pull request
>
> These fixes make dataplane work again after the notify_me optimization was
> added. They also solve QEMUBH memory leaks and fix a bug in dataplane's
> cleanup code.
Applied, thanks.
-- PMM
prev parent reply other threads:[~2015-07-29 17:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 13:50 [Qemu-devel] [PULL for-2.4 0/3] Block patches Stefan Hajnoczi
2015-07-29 13:50 ` [Qemu-devel] [PULL for-2.4 1/3] virtio-blk-dataplane: delete bottom half before the AioContext is freed Stefan Hajnoczi
2015-07-29 13:50 ` [Qemu-devel] [PULL for-2.4 2/3] AioContext: avoid leaking BHs on cleanup Stefan Hajnoczi
2015-07-29 13:50 ` [Qemu-devel] [PULL for-2.4 3/3] AioContext: force event loop iteration using BH Stefan Hajnoczi
2015-07-29 17:49 ` 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=CAFEAcA8P_anW1NbC0FcxzHSCoRXaKgs_OWikuWkprkFXT7DNgw@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=kwolf@redhat.com \
--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).