From: Klaus Jensen <its@irrelevant.dk>
To: qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, Klaus Jensen <its@irrelevant.dk>,
Keith Busch <kbusch@kernel.org>,
Klaus Jensen <k.jensen@samsung.com>
Subject: [PULL 0/2] hw/nvme fixes
Date: Wed, 2 Nov 2022 09:25:53 +0100 [thread overview]
Message-ID: <20221102082555.65165-1-its@irrelevant.dk> (raw)
From: Klaus Jensen <k.jensen@samsung.com>
Hi,
The following changes since commit a11f65ec1b8adcb012b89c92819cbda4dc25aaf1:
Merge tag 'block-pull-request' of https://gitlab.com/stefanha/qemu into staging (2022-11-01 13:49:33 -0400)
are available in the Git repository at:
git://git.infradead.org/qemu-nvme.git tags/nvme-fixes-pull-request
for you to fetch changes up to 632cb6cf07122b330d8ef419ec2f4aab561a9fba:
hw/nvme: Abort copy command when format is one while pif (2022-11-02 09:23:05 +0100)
----------------------------------------------------------------
hw/nvme fixes
Two small fixes.
----------------------------------------------------------------
Francis Pravin Antony Michael Raj (1):
hw/nvme: Abort copy command when format is one while pif
Klaus Jensen (1):
hw/nvme: reenable cqe batching
hw/nvme/ctrl.c | 29 +++++++++++++----------------
hw/nvme/nvme.h | 4 ++--
2 files changed, 15 insertions(+), 18 deletions(-)
--
2.38.1
next reply other threads:[~2022-11-02 8:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 8:25 Klaus Jensen [this message]
2022-11-02 8:25 ` [PULL 1/2] hw/nvme: reenable cqe batching Klaus Jensen
2022-11-02 8:25 ` [PULL 2/2] hw/nvme: Abort copy command when format is one while pif Klaus Jensen
2022-11-03 21:26 ` [PULL 0/2] hw/nvme fixes Stefan Hajnoczi
-- strict thread matches above, loose matches on Subject: below --
2023-03-27 17:09 Klaus Jensen
2023-03-28 16:00 ` Peter Maydell
2023-08-07 11:54 Klaus Jensen
2023-08-07 20:36 ` 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=20221102082555.65165-1-its@irrelevant.dk \
--to=its@irrelevant.dk \
--cc=k.jensen@samsung.com \
--cc=kbusch@kernel.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 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).