From: Peter Maydell <peter.maydell@linaro.org>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Qemu-block <qemu-block@nongnu.org>,
Richard Henderson <rth@twiddle.net>,
Peter Crosthwaite <crosthwaite.peter@gmail.com>,
Fam Zheng <famz@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Max Reitz <mreitz@redhat.com>, Kevin Wolf <kwolf@redhat.com>
Subject: Re: [Qemu-devel] [PULL 0/1] Block patches
Date: Tue, 13 Mar 2018 11:42:34 +0000 [thread overview]
Message-ID: <CAFEAcA9zfh+QXf_DFW+LyNnMVkQpZzZD5cCmG5jaeKpPHQ3Jrw@mail.gmail.com> (raw)
In-Reply-To: <20180312160125.7596-1-stefanha@redhat.com>
On 12 March 2018 at 16:01, Stefan Hajnoczi <stefanha@redhat.com> wrote:
> The following changes since commit e4ae62b802cec437f877f2cadc4ef059cc0eca76:
>
> Merge remote-tracking branch 'remotes/stefanha/tags/block-pull-request' into staging (2018-03-09 17:28:16 +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 7376eda7c2e0451e819e81bd05fabc56a9deb946:
>
> block: make BDRV_POLL_WHILE() re-entrancy safe (2018-03-12 11:07:37 +0000)
>
> ----------------------------------------------------------------
>
> ----------------------------------------------------------------
>
> Stefan Hajnoczi (1):
> block: make BDRV_POLL_WHILE() re-entrancy safe
>
> include/block/aio-wait.h | 61 ++++++++++++++++++++++++------------------------
> util/aio-wait.c | 2 +-
> 2 files changed, 31 insertions(+), 32 deletions(-)
Applied, thanks.
-- PMM
next prev parent reply other threads:[~2018-03-13 11:42 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 16:01 [Qemu-devel] [PULL 0/1] Block patches Stefan Hajnoczi
2018-03-12 16:01 ` [Qemu-devel] [PULL 1/1] block: make BDRV_POLL_WHILE() re-entrancy safe Stefan Hajnoczi
2018-03-13 11:42 ` Peter Maydell [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-09-11 14:36 [Qemu-devel] [PULL 0/1] Block patches Stefan Hajnoczi
2019-09-13 12:43 ` Peter Maydell
2019-06-28 13:13 Stefan Hajnoczi
2019-07-02 9:59 ` Peter Maydell
2019-02-14 4:33 Stefan Hajnoczi
2019-02-14 17:41 ` Peter Maydell
2018-06-13 14:53 Jeff Cody
2018-06-14 13:04 ` Peter Maydell
2018-03-13 12:29 Jeff Cody
2018-03-15 10:00 ` Peter Maydell
2017-11-06 11:20 Stefan Hajnoczi
2017-11-06 12:07 ` Peter Maydell
2017-10-20 12:02 Stefan Hajnoczi
2017-10-20 16:36 ` Peter Maydell
2017-06-09 12:43 Jeff Cody
2017-06-13 12:51 ` Peter Maydell
2017-06-02 15:33 Jeff Cody
2017-06-02 16:46 ` Peter Maydell
2017-02-03 14:37 Stefan Hajnoczi
2017-02-03 15:20 ` Peter Maydell
2017-02-01 13:24 Stefan Hajnoczi
2017-02-02 16:07 ` Peter Maydell
2017-02-03 14:33 ` Stefan Hajnoczi
2017-01-26 10:19 Stefan Hajnoczi
2017-01-27 13:30 ` Peter Maydell
2016-11-15 15:42 Stefan Hajnoczi
2016-11-15 16:17 ` Stefan Hajnoczi
2016-08-11 10:35 Stefan Hajnoczi
2016-08-11 12:26 ` Peter Maydell
2016-05-17 0:19 Stefan Hajnoczi
2016-05-17 15:48 ` Peter Maydell
2015-11-11 18:00 Jeff Cody
2015-11-12 10:07 ` 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=CAFEAcA9zfh+QXf_DFW+LyNnMVkQpZzZD5cCmG5jaeKpPHQ3Jrw@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=crosthwaite.peter@gmail.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.