From: Klaus Jensen <its@irrelevant.dk>
To: qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, Klaus Jensen <k.jensen@samsung.com>,
Max Reitz <mreitz@redhat.com>, Keith Busch <kbusch@kernel.org>,
Klaus Jensen <its@irrelevant.dk>
Subject: [PULL for-6.0 0/2] emulated nvme fixes
Date: Mon, 29 Mar 2021 19:04:47 +0200 [thread overview]
Message-ID: <20210329170449.125958-1-its@irrelevant.dk> (raw)
From: Klaus Jensen <k.jensen@samsung.com>
Hi Peter,
The following changes since commit ec2e6e016d24bd429792d08cf607e4c5350dcdaa:
Merge remote-tracking branch 'remotes/vivier2/tags/linux-user-for-6.0-pull-request' into staging (2021-03-28 19:49:57 +0100)
are available in the Git repository at:
git://git.infradead.org/qemu-nvme.git tags/nvme-fixes-for-6.0-pull-request
for you to fetch changes up to 3a69cadbef7af23a566dbe2400043c247c3d50ca:
hw/block/nvme: fix ref counting in nvme_format_ns (2021-03-29 18:46:57 +0200)
----------------------------------------------------------------
emulated nvme fixes
----------------------------------------------------------------
Klaus Jensen (2):
hw/block/nvme: fix resource leak in nvme_dif_rw
hw/block/nvme: fix ref counting in nvme_format_ns
hw/block/nvme-dif.c | 2 +-
hw/block/nvme.c | 10 ++++++++--
2 files changed, 9 insertions(+), 3 deletions(-)
--
2.31.0
next reply other threads:[~2021-03-29 17:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 17:04 Klaus Jensen [this message]
2021-03-29 17:04 ` [PULL for-6.0 1/2] hw/block/nvme: fix resource leak in nvme_dif_rw Klaus Jensen
2021-03-29 17:04 ` [PULL for-6.0 2/2] hw/block/nvme: fix ref counting in nvme_format_ns Klaus Jensen
2021-03-30 12:08 ` [PULL for-6.0 0/2] emulated nvme fixes Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2021-04-05 17:34 Klaus Jensen
2021-04-06 9:34 ` Peter Maydell
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=20210329170449.125958-1-its@irrelevant.dk \
--to=its@irrelevant.dk \
--cc=k.jensen@samsung.com \
--cc=kbusch@kernel.org \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=peter.maydell@linaro.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).