From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
Hanna Reitz <hreitz@redhat.com>,
qemu-block@nongnu.org
Subject: Re: [PULL 0/1] Block patches
Date: Wed, 7 Feb 2024 23:19:00 +0100 [thread overview]
Message-ID: <ZcQB1FH8Kqt5xn0v@redhat.com> (raw)
In-Reply-To: <20240206153105.81868-1-stefanha@redhat.com>
Am 06.02.2024 um 16:31 hat Stefan Hajnoczi geschrieben:
> The following changes since commit 39a6e4f87e7b75a45b08d6dc8b8b7c2954c87440:
>
> Merge tag 'pull-qapi-2024-02-03' of https://repo.or.cz/qemu/armbru into staging (2024-02-03 13:31:58 +0000)
>
> are available in the Git repository at:
>
> https://gitlab.com/stefanha/qemu.git tags/block-pull-request
>
> for you to fetch changes up to 1d52cc0ac27761e296b14655c2f5b2649ee69491:
>
> virtio-blk: avoid using ioeventfd state in irqfd conditional (2024-02-06 10:22:18 -0500)
>
> ----------------------------------------------------------------
> Pull request
>
> A bug fix for in-flight I/O during ioeventfd shutdown.
>
> ----------------------------------------------------------------
>
> Stefan Hajnoczi (1):
> virtio-blk: avoid using ioeventfd state in irqfd conditional
I noticed that this patch is also in the pull request I sent, so I
guess if mine goes through, you don't have to process this one
separately.
Kevin
next prev parent reply other threads:[~2024-02-07 22:20 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 15:31 [PULL 0/1] Block patches Stefan Hajnoczi
2024-02-06 15:31 ` [PULL 1/1] virtio-blk: avoid using ioeventfd state in irqfd conditional Stefan Hajnoczi
2024-02-08 5:37 ` Michael Tokarev
2024-02-08 8:42 ` Kevin Wolf
2024-02-08 9:01 ` Michael Tokarev
2024-02-07 22:19 ` Kevin Wolf [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-05-25 15:18 [PULL 0/1] Block patches Stefan Hajnoczi
2026-05-26 18:52 ` Stefan Hajnoczi
2025-10-27 19:05 Stefan Hajnoczi
2025-10-28 12:11 ` Richard Henderson
2025-10-06 14:59 Stefan Hajnoczi
2025-10-06 21:59 ` Richard Henderson
2025-04-30 15:47 Stefan Hajnoczi
2025-04-30 19:04 ` Stefan Hajnoczi
2025-05-01 13:03 ` Peter Maydell
2025-03-06 2:21 Stefan Hajnoczi
2025-03-07 7:18 ` Stefan Hajnoczi
2025-01-30 20:33 Stefan Hajnoczi
2025-02-02 17:49 ` Stefan Hajnoczi
2024-09-17 11:43 Stefan Hajnoczi
2024-09-17 14:48 ` Peter Maydell
2024-08-12 15:55 Stefan Hajnoczi
2024-08-13 5:01 ` Richard Henderson
2024-07-25 20:12 Stefan Hajnoczi
2024-07-26 5:12 ` Richard Henderson
2024-04-29 13:43 Stefan Hajnoczi
2024-03-19 15:09 Stefan Hajnoczi
2024-03-19 19:11 ` Peter Maydell
2023-10-16 19:40 Stefan Hajnoczi
2023-10-04 13:53 Stefan Hajnoczi
2023-10-04 18:33 ` Stefan Hajnoczi
2023-07-12 19:36 Stefan Hajnoczi
2023-07-14 6:35 ` Richard Henderson
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=ZcQB1FH8Kqt5xn0v@redhat.com \
--to=kwolf@redhat.com \
--cc=hreitz@redhat.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.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 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.