From: Klaus Jensen <its@irrelevant.dk>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: qemu-devel@nongnu.org, libvir-list@redhat.com,
Keith Busch <kbusch@kernel.org>,
qemu-block@nongnu.org, Klaus Jensen <k.jensen@samsung.com>
Subject: Re: [PATCH] hw/nvme: deprecate the use-intel-id compatibility parameter
Date: Mon, 30 May 2022 21:31:27 +0200 [thread overview]
Message-ID: <YpUbj1WDrGDBFc8d@apples> (raw)
In-Reply-To: <fc24ead8-4495-f67d-6fb0-c2d11bf94684@amsat.org>
[-- Attachment #1: Type: text/plain, Size: 1543 bytes --]
On May 30 16:37, Philippe Mathieu-Daudé wrote:
> On 29/4/22 07:41, Klaus Jensen wrote:
> > From: Klaus Jensen <k.jensen@samsung.com>
> >
> > Since version 5.2 commit 6eb7a071292a ("hw/block/nvme: change controller
> > pci id"), the emulated NVMe controller has defaulted to a non-Intel PCI
> > identifier.
> >
> > Deprecate the compatibility parameter so we can get rid of it once and
> > for all.
> >
> > Signed-off-by: Klaus Jensen <k.jensen@samsung.com>
> > ---
> > docs/about/deprecated.rst | 8 ++++++++
> > 1 file changed, 8 insertions(+)
> >
> > diff --git a/docs/about/deprecated.rst b/docs/about/deprecated.rst
> > index 896e5a97abbd..450f945ac25f 100644
> > --- a/docs/about/deprecated.rst
> > +++ b/docs/about/deprecated.rst
> > @@ -356,6 +356,14 @@ contains native support for this feature and thus use of the option
> > ROM approach is obsolete. The native SeaBIOS support can be activated
> > by using ``-machine graphics=off``.
> > +``-device nvme,use-intel-id=on|off`` (since 7.1)
> > +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > +
> > +The ``nvme`` device originally used a PCI Vendor/Device Identifier combination
> > +from Intel that was not properly allocated. Since version 5.2, the controller
> > +has used a properly allocated identifier. Deprecate the ``use-intel-id``
> > +machine compatibility parameter.
> > +
> > Block device options
> > ''''''''''''''''''''
>
> Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Thanks!
Applied to nvme-next.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2022-05-30 19:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 5:41 [PATCH] hw/nvme: deprecate the use-intel-id compatibility parameter Klaus Jensen
2022-05-30 14:37 ` Philippe Mathieu-Daudé via
2022-05-30 19:31 ` Klaus Jensen [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=YpUbj1WDrGDBFc8d@apples \
--to=its@irrelevant.dk \
--cc=f4bug@amsat.org \
--cc=k.jensen@samsung.com \
--cc=kbusch@kernel.org \
--cc=libvir-list@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).