From: Klaus Jensen <its@irrelevant.dk>
To: Niklas Cassel <niklas.cassel@wdc.com>
Cc: kbusch@kernel.org, qemu-block@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH] hw/nvme: fix example serial in documentation
Date: Mon, 27 Jun 2022 19:11:51 +0200 [thread overview]
Message-ID: <Yrnk13dtEptPYVIA@apples> (raw)
In-Reply-To: <20220627123957.363889-1-niklas.cassel@wdc.com>
[-- Attachment #1: Type: text/plain, Size: 1367 bytes --]
On Jun 27 14:39, Niklas Cassel wrote:
> The serial prop on the controller is actually describing the nvme
> subsystem serial, which has to be identical for all controllers within
> the same nvme subsystem.
>
> This is enforced since commit a859eb9f8f64 ("hw/nvme: enforce common
> serial per subsystem").
>
> Fix the documentation, so that people copying the qemu command line
> example won't get an error on qemu start.
>
> Signed-off-by: Niklas Cassel <niklas.cassel@wdc.com>
> ---
> docs/system/devices/nvme.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/docs/system/devices/nvme.rst b/docs/system/devices/nvme.rst
> index aba253304e..30f841ef62 100644
> --- a/docs/system/devices/nvme.rst
> +++ b/docs/system/devices/nvme.rst
> @@ -104,8 +104,8 @@ multipath I/O.
> .. code-block:: console
>
> -device nvme-subsys,id=nvme-subsys-0,nqn=subsys0
> - -device nvme,serial=a,subsys=nvme-subsys-0
> - -device nvme,serial=b,subsys=nvme-subsys-0
> + -device nvme,serial=deadbeef,subsys=nvme-subsys-0
> + -device nvme,serial=deadbeef,subsys=nvme-subsys-0
>
> This will create an NVM subsystem with two controllers. Having controllers
> linked to an ``nvme-subsys`` device allows additional ``nvme-ns`` parameters:
> --
> 2.36.1
>
Woops!
Thanks Niklas, applied to nvme-next!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-06-27 17:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 12:39 [PATCH] hw/nvme: fix example serial in documentation Niklas Cassel via
2022-06-27 17:11 ` Klaus Jensen [this message]
2022-06-28 12:26 ` Daniel P. Berrangé
2022-06-28 12:31 ` 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=Yrnk13dtEptPYVIA@apples \
--to=its@irrelevant.dk \
--cc=kbusch@kernel.org \
--cc=niklas.cassel@wdc.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).