From: Klaus Jensen <its@irrelevant.dk>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Klaus Jensen <k.jensen@samsung.com>
Subject: [PULL 0/2] hw/nvme fixes
Date: Thu, 26 Mar 2026 09:23:47 +0100 [thread overview]
Message-ID: <20260326082350.17374-1-its@irrelevant.dk> (raw)
From: Klaus Jensen <k.jensen@samsung.com>
Hi,
The following changes since commit 007b29752ed06e467d3c830bc2c17a8851f8bcd3:
Merge tag 'for-upstream' of https://gitlab.com/kmwolf/qemu into staging (2026-03-25 09:16:13 +0000)
are available in the Git repository at:
https://gitlab.com/birkelund/qemu.git tags/pull-nvme-20260326
for you to fetch changes up to eb5cc99aff17cbfdad16b18d3503c6f22233eeb5:
hw/nvme: fix heap-buffer-overflow in nvme_abort (2026-03-26 09:14:35 +0100)
----------------------------------------------------------------
nvme queue
----------------------------------------------------------------
Kaixuan Li (1):
hw/nvme: fix heap-buffer-overflow in nvme_abort
Pankaj Raghav (1):
hw/nvme: re-enable wzds bit in namespace dlfeat
hw/nvme/ctrl.c | 4 +++-
hw/nvme/ns.c | 2 +-
2 files changed, 4 insertions(+), 2 deletions(-)
next reply other threads:[~2026-03-26 8:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 8:23 Klaus Jensen [this message]
2026-03-26 8:23 ` [PULL 1/2] hw/nvme: re-enable wzds bit in namespace dlfeat Klaus Jensen
2026-03-28 6:57 ` Michael Tokarev
2026-03-30 9:06 ` Klaus Jensen
2026-03-26 8:23 ` [PULL 2/2] hw/nvme: fix heap-buffer-overflow in nvme_abort Klaus Jensen
2026-03-26 14:58 ` [PULL 0/2] hw/nvme fixes Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2023-08-07 11:54 Klaus Jensen
2023-08-07 20:36 ` Richard Henderson
2023-03-27 17:09 Klaus Jensen
2023-03-28 16:00 ` Peter Maydell
2022-11-02 8:25 Klaus Jensen
2022-11-03 21:26 ` Stefan Hajnoczi
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=20260326082350.17374-1-its@irrelevant.dk \
--to=its@irrelevant.dk \
--cc=k.jensen@samsung.com \
--cc=peter.maydell@linaro.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.