From: Klaus Jensen <its@irrelevant.dk>
To: qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Cc: Keith Busch <kbusch@kernel.org>,
qemu-block@nongnu.org, Klaus Jensen <its@irrelevant.dk>,
Klaus Jensen <k.jensen@samsung.com>
Subject: [PULL for-7.1 0/3] hw/nvme fixes
Date: Mon, 1 Aug 2022 12:05:53 +0200 [thread overview]
Message-ID: <20220801100556.2217492-1-its@irrelevant.dk> (raw)
From: Klaus Jensen <k.jensen@samsung.com>
Hi,
The following changes since commit 3916603e0c1d909e14e09d5ebcbdaa9c9e21adf3:
Merge tag 'pull-la-20220729' of https://gitlab.com/rth7680/qemu into staging (2022-07-29 17:39:17 -0700)
are available in the Git repository at:
git://git.infradead.org/qemu-nvme.git tags/nvme-next-pull-request
for you to fetch changes up to e2e137f64282a2ee2f359b6df4cd93c83a308e7b:
hw/nvme: do not enable ioeventfd by default (2022-08-01 12:01:21 +0200)
----------------------------------------------------------------
hw/nvme fixes
Some fixes for hw/nvme ioeventfd support.
----------------------------------------------------------------
Klaus Jensen (3):
hw/nvme: skip queue processing if notifier is cleared
hw/nvme: unregister the event notifier handler on the main loop
hw/nvme: do not enable ioeventfd by default
hw/nvme/ctrl.c | 12 +++++++++---
1 file changed, 9 insertions(+), 3 deletions(-)
--
2.36.1
next reply other threads:[~2022-08-01 10:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 10:05 Klaus Jensen [this message]
2022-08-01 10:05 ` [PULL for-7.1 1/3] hw/nvme: skip queue processing if notifier is cleared Klaus Jensen
2022-08-01 10:05 ` [PULL for-7.1 2/3] hw/nvme: unregister the event notifier handler on the main loop Klaus Jensen
2022-08-01 10:05 ` [PULL for-7.1 3/3] hw/nvme: do not enable ioeventfd by default Klaus Jensen
2022-08-01 15:49 ` [PULL for-7.1 0/3] hw/nvme fixes Richard Henderson
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=20220801100556.2217492-1-its@irrelevant.dk \
--to=its@irrelevant.dk \
--cc=k.jensen@samsung.com \
--cc=kbusch@kernel.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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.