qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: Klaus Jensen <its@irrelevant.dk>, qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, Keith Busch <kbusch@kernel.org>,
	Klaus Jensen <k.jensen@samsung.com>
Subject: Re: [PULL 0/2] hw/nvme: more fixes
Date: Wed, 9 Aug 2023 15:04:11 -0700	[thread overview]
Message-ID: <095cf8cf-f0b4-02ad-b555-e52e67343b4e@linaro.org> (raw)
In-Reply-To: <20230809133909.45818-4-its@irrelevant.dk>

On 8/9/23 06:39, Klaus Jensen wrote:
> From: Klaus Jensen<k.jensen@samsung.com>
> 
> Hi,
> 
> The following changes since commit a8fc5165aab02f328ccd148aafec1e59fd1426eb:
> 
>    Merge tag 'nvme-next-pull-request' ofhttps://gitlab.com/birkelund/qemu  into staging (2023-08-08 16:39:20 -0700)
> 
> are available in the Git repository at:
> 
>    https://gitlab.com/birkelund/qemu.git  tags/nvme-fixes-pull-request
> 
> for you to fetch changes up to 3439ba9c5da943d96f7a3c86e0a7eb2ff48de41c:
> 
>    hw/nvme: fix null pointer access in ruh update (2023-08-09 15:32:32 +0200)
> 
> ----------------------------------------------------------------
> hw/nvme: fixes

Applied, thanks.  Please update https://wiki.qemu.org/ChangeLog/8.1 as appropriate.


r~



      parent reply	other threads:[~2023-08-09 22:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-09 13:39 [PULL 0/2] hw/nvme: more fixes Klaus Jensen
2023-08-09 13:39 ` [PULL 1/2] hw/nvme: fix null pointer access in directive receive Klaus Jensen
2023-08-24 12:44   ` Philippe Mathieu-Daudé
2023-08-24 13:08     ` Michael Tokarev
2023-08-24 13:27     ` Klaus Jensen
2023-08-09 13:39 ` [PULL 2/2] hw/nvme: fix null pointer access in ruh update Klaus Jensen
2023-08-09 22:04 ` Richard Henderson [this message]

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=095cf8cf-f0b4-02ad-b555-e52e67343b4e@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=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).