From: Peter Maydell <peter.maydell@linaro.org>
To: Klaus Jensen <its@irrelevant.dk>
Cc: qemu-devel@nongnu.org, Klaus Jensen <k.jensen@samsung.com>
Subject: Re: [PULL 0/2] hw/nvme fixes
Date: Thu, 26 Mar 2026 14:58:44 +0000 [thread overview]
Message-ID: <CAFEAcA9MULr1GcGhCnZRbK2VCRczaiR2ppCHYeWdddP+LeX9OQ@mail.gmail.com> (raw)
In-Reply-To: <20260326082350.17374-1-its@irrelevant.dk>
On Thu, 26 Mar 2026 at 08:24, Klaus Jensen <its@irrelevant.dk> wrote:
>
> 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
>
> ----------------------------------------------------------------
Applied, thanks.
Please update the changelog at https://wiki.qemu.org/ChangeLog/11.0
for any user-visible changes.
-- PMM
next prev parent reply other threads:[~2026-03-26 14:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 8:23 [PULL 0/2] hw/nvme fixes Klaus Jensen
2026-03-26 8:23 ` [PULL 1/2] hw/nvme: re-enable wzds bit in namespace dlfeat 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 ` Peter Maydell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-07 11:54 [PULL 0/2] hw/nvme fixes 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=CAFEAcA9MULr1GcGhCnZRbK2VCRczaiR2ppCHYeWdddP+LeX9OQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=its@irrelevant.dk \
--cc=k.jensen@samsung.com \
--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