All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: Stefan Hajnoczi <stefanha@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
	qemu-block@nongnu.org, Hanna Reitz <hreitz@redhat.com>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [PULL 0/1] Block patches
Date: Fri, 14 Jul 2023 07:35:40 +0100	[thread overview]
Message-ID: <25613abf-11e9-f836-3e6e-92eef203af9d@linaro.org> (raw)
In-Reply-To: <20230712193658.255676-1-stefanha@redhat.com>

On 7/12/23 20:36, Stefan Hajnoczi wrote:
> The following changes since commit 887cba855bb6ff4775256f7968409281350b568c:
> 
>    configure: Fix cross-building for RISCV host (v5) (2023-07-11 17:56:09 +0100)
> 
> are available in the Git repository at:
> 
>    https://gitlab.com/stefanha/qemu.git tags/block-pull-request
> 
> for you to fetch changes up to 75dcb4d790bbe5327169fd72b185960ca58e2fa6:
> 
>    virtio-blk: fix host notifier issues during dataplane start/stop (2023-07-12 15:20:32 -0400)
> 
> ----------------------------------------------------------------
> Pull request
> 
> ----------------------------------------------------------------
> 
> Stefan Hajnoczi (1):
>    virtio-blk: fix host notifier issues during dataplane start/stop
> 
>   hw/block/dataplane/virtio-blk.c | 67 +++++++++++++++++++--------------
>   1 file changed, 38 insertions(+), 29 deletions(-)
> 

Applied, thanks.  Please update https://wiki.qemu.org/ChangeLog/8.1 as appropriate.


r~



  parent reply	other threads:[~2023-07-14  6:36 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-12 19:36 [PULL 0/1] Block patches Stefan Hajnoczi
2023-07-12 19:36 ` [PULL 1/1] virtio-blk: fix host notifier issues during dataplane start/stop Stefan Hajnoczi
2023-07-14  6:35 ` Richard Henderson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-29 13:43 [PULL 0/1] Block patches Stefan Hajnoczi
2024-03-19 15:09 Stefan Hajnoczi
2024-03-19 19:11 ` Peter Maydell
2024-02-06 15:31 Stefan Hajnoczi
2024-02-07 22:19 ` Kevin Wolf
2023-10-16 19:40 Stefan Hajnoczi
2023-10-04 13:53 Stefan Hajnoczi
2023-10-04 18:33 ` Stefan Hajnoczi
2023-07-04 15:29 Stefan Hajnoczi
2023-07-06  6:04 ` Richard Henderson
2022-09-22 17:14 Stefan Hajnoczi
2022-09-27 15:04 ` Stefan Hajnoczi
2022-05-25 12:49 Stefan Hajnoczi
2022-05-25 18:35 ` Richard Henderson
2021-12-09 15:21 Stefan Hajnoczi
2021-12-09 15:46 ` Peter Maydell
2021-12-09 16:34   ` Stefan Hajnoczi
2021-12-09 16:53     ` Richard Henderson
2021-12-13  9:33       ` Stefan Hajnoczi
2021-12-14 22:31 ` Richard Henderson
2021-12-06 15:27 Stefan Hajnoczi
2021-12-06 21:16 ` Richard Henderson
2021-10-21 17:41 Stefan Hajnoczi
2021-10-21 22:08 ` Richard Henderson
2021-10-25 10:10   ` Stefan Hajnoczi
2021-03-15  9:51 Stefan Hajnoczi
2021-03-15 22:01 ` Peter Maydell
2021-01-04 14:23 Stefan Hajnoczi
2021-01-04 17:17 ` Peter Maydell
2020-03-17 15:18 Stefan Hajnoczi
2020-03-17 18:32 ` Peter Maydell
2020-01-14  9:30 Stefan Hajnoczi
2020-01-14 16:00 ` Peter Maydell
2019-10-14  8:52 Stefan Hajnoczi
2019-10-15 11:00 ` 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=25613abf-11e9-f836-3e6e-92eef203af9d@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=hreitz@redhat.com \
    --cc=kwolf@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.