From: Niklas Cassel <Niklas.Cassel@wdc.com>
To: Klaus Jensen <its@irrelevant.dk>
Cc: Kevin Wolf <kwolf@redhat.com>,
"qemu-block@nongnu.org" <qemu-block@nongnu.org>,
Dmitry Fomichev <Dmitry.Fomichev@wdc.com>,
Klaus Jensen <k.jensen@samsung.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Max Reitz <mreitz@redhat.com>, Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCH 0/2] hw/block/nvme: zoned fixes
Date: Wed, 20 Jan 2021 11:10:58 +0000 [thread overview]
Message-ID: <20210120111057.GA126026@localhost.localdomain> (raw)
In-Reply-To: <20210119135500.265403-1-its@irrelevant.dk>
On Tue, Jan 19, 2021 at 02:54:58PM +0100, Klaus Jensen wrote:
> From: Klaus Jensen <k.jensen@samsung.com>
>
> Patch [1/2] fixes the zone append bug reported by Niklas. [2/2]
> refactors the zone write check function to return status codes in a
> different order if there are multiple zone write violations that apply.
>
> Klaus Jensen (2):
> hw/block/nvme: fix zone boundary check for append
> hw/block/nvme: refactor the logic for zone write checks
>
> hw/block/nvme.c | 89 +++++++++++++++++++++----------------------
> hw/block/trace-events | 5 +++
> 2 files changed, 48 insertions(+), 46 deletions(-)
>
> --
> 2.30.0
>
>
For the series:
Tested-by: Niklas Cassel <niklas.cassel@wdc.com>
next prev parent reply other threads:[~2021-01-20 11:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 13:54 [PATCH 0/2] hw/block/nvme: zoned fixes Klaus Jensen
2021-01-19 13:54 ` [PATCH 1/2] hw/block/nvme: fix zone boundary check for append Klaus Jensen
2021-01-26 4:55 ` Dmitry Fomichev
2021-01-26 6:58 ` Klaus Jensen
2021-01-19 13:55 ` [PATCH 2/2] hw/block/nvme: refactor the logic for zone write checks Klaus Jensen
2021-01-26 4:58 ` Dmitry Fomichev
2021-01-20 11:10 ` Niklas Cassel [this message]
2021-01-25 7:25 ` [PATCH 0/2] hw/block/nvme: zoned fixes Klaus Jensen
2021-01-25 21:48 ` Dmitry Fomichev
2021-01-27 17:42 ` Keith Busch
2021-01-27 23:30 ` Dmitry Fomichev
2021-01-28 6:24 ` Klaus Jensen
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=20210120111057.GA126026@localhost.localdomain \
--to=niklas.cassel@wdc.com \
--cc=Dmitry.Fomichev@wdc.com \
--cc=its@irrelevant.dk \
--cc=k.jensen@samsung.com \
--cc=kbusch@kernel.org \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--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).