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/3] nvme fixes
Date: Mon, 11 Aug 2025 13:25:54 +0200 [thread overview]
Message-ID: <20250811112557.521-1-its@irrelevant.dk> (raw)
From: Klaus Jensen <k.jensen@samsung.com>
Hi,
The following changes since commit a74434580e1051bff12ab5eee5586058295c497f:
Merge tag 'pull-loongarch-20250808' of https://github.com/gaosong715/qemu into staging (2025-08-08 09:49:06 -0400)
are available in the Git repository at:
https://gitlab.com/birkelund/qemu.git tags/pull-nvme-20250811
for you to fetch changes up to 53493c1f836f4dda90a6b5f2fb3d9264918c6871:
hw/nvme: cap MDTS value for internal limitation (2025-08-11 00:17:38 -0700)
----------------------------------------------------------------
nvme queue
----------------------------------------------------------------
Keith Busch (1):
hw/nvme: cap MDTS value for internal limitation
Klaus Jensen (2):
hw/nvme: fix namespace attachment
hw/nvme: revert CMIC behavior
hw/nvme/ctrl.c | 43 ++++++++++++++++++++++++++++---------------
1 file changed, 28 insertions(+), 15 deletions(-)
next reply other threads:[~2025-08-11 11:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 11:25 Klaus Jensen [this message]
2025-08-11 11:25 ` [PULL 1/3] hw/nvme: fix namespace attachment Klaus Jensen
2025-08-11 11:25 ` [PULL 2/3] hw/nvme: revert CMIC behavior Klaus Jensen
2025-08-11 11:25 ` [PULL 3/3] hw/nvme: cap MDTS value for internal limitation Klaus Jensen
2025-08-11 20:43 ` [PULL 0/3] nvme fixes Stefan Hajnoczi
2025-08-12 5:49 ` Michael Tokarev
2025-09-05 7:57 ` Michael Tokarev
2025-09-05 7:59 ` Klaus Jensen
-- strict thread matches above, loose matches on Subject: below --
2025-11-25 8:47 Klaus Jensen
2025-11-25 18:22 ` 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=20250811112557.521-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.