All of lore.kernel.org
 help / color / mirror / Atom feed
From: Klaus Jensen <its@irrelevant.dk>
To: "info@dantalion.nl" <info@dantalion.nl>
Cc: Kevin Wolf <kwolf@redhat.com>,
	qemu-block@nongnu.org, Dmitry Fomichev <Dmitry.Fomichev@wdc.com>,
	Klaus Jensen <k.jensen@samsung.com>,
	qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>,
	Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCH] hw/block/nvme: improve invalid zasl value reporting
Date: Mon, 8 Feb 2021 10:19:00 +0100	[thread overview]
Message-ID: <YCECBCV5LbTbYn84@apples.localdomain> (raw)
In-Reply-To: <75433660-5650-8598-2143-4158113acb8e@dantalion.nl>

[-- Attachment #1: Type: text/plain, Size: 572 bytes --]

On Feb  8 10:15, info@dantalion.nl wrote:
> On 08-02-2021 09:25, Klaus Jensen wrote:
> > The Zone Append Size Limit (ZASL) must be at least 4096 bytes, so
> > improve the user experience by adding an early parameter check in
> > nvme_check_constraints.
> 
> I have confirmed this and it works for me, I don't think I am actually
> qualified or understand QEMUs source well enough to sign this off but
> just wanted to let you know.
> 
> Thanks for the quick updates.
> 

I'll add a 'Tested-by: ...' tag from you.

Thanks for reporting and following up! ;)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2021-02-08 16:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-08  8:25 [PATCH] hw/block/nvme: improve invalid zasl value reporting Klaus Jensen
2021-02-08  9:15 ` info
2021-02-08  9:19   ` Klaus Jensen [this message]
2021-02-09 19:39 ` Dmitry Fomichev
2021-02-10  6:09   ` Philippe Mathieu-Daudé
2021-02-10 20:56 ` 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=YCECBCV5LbTbYn84@apples.localdomain \
    --to=its@irrelevant.dk \
    --cc=Dmitry.Fomichev@wdc.com \
    --cc=info@dantalion.nl \
    --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 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.