From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Chen Zhang <tgfbeta@me.com>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, Alex Williamson <alex.williamson@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] vfio: fix a typo
Date: Thu, 22 Aug 2019 10:45:01 +0200 [thread overview]
Message-ID: <a448f7da-c990-7dc5-e5ab-139994dfc814@redhat.com> (raw)
In-Reply-To: <8E5A9C27-C76D-46CF-85B0-79121A00B05F@me.com>
On 8/22/19 8:49 AM, Chen Zhang via Qemu-devel wrote:
> Signed-off-by: Chen Zhang <tgfbeta@me.com>
> ---
> hw/vfio/pci.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/hw/vfio/pci.c b/hw/vfio/pci.c
> index dc3479c..c5e6fe6 100644
> --- a/hw/vfio/pci.c
> +++ b/hw/vfio/pci.c
> @@ -44,7 +44,7 @@
> #define TYPE_VFIO_PCI "vfio-pci"
> #define PCI_VFIO(obj) OBJECT_CHECK(VFIOPCIDevice, obj, TYPE_VFIO_PCI)
>
> -#define TYPE_VIFO_PCI_NOHOTPLUG "vfio-pci-nohotplug"
> +#define TYPE_VFIO_PCI_NOHOTPLUG "vfio-pci-nohotplug"
>
> static void vfio_disable_interrupts(VFIOPCIDevice *vdev);
> static void vfio_mmap_set_enabled(VFIOPCIDevice *vdev, bool enabled);
> @@ -3199,7 +3199,7 @@ static void vfio_pci_nohotplug_dev_class_init(ObjectClass *klass, void *data)
> }
>
> static const TypeInfo vfio_pci_nohotplug_dev_info = {
> - .name = TYPE_VIFO_PCI_NOHOTPLUG,
> + .name = TYPE_VFIO_PCI_NOHOTPLUG,
> .parent = TYPE_VFIO_PCI,
> .instance_size = sizeof(VFIOPCIDevice),
> .class_init = vfio_pci_nohotplug_dev_class_init,
>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
next prev parent reply other threads:[~2019-08-22 8:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 6:49 [Qemu-devel] [PATCH] vfio: fix a typo Chen Zhang via Qemu-devel
2019-08-22 7:53 ` Li Qiang
2019-08-22 8:45 ` Philippe Mathieu-Daudé [this message]
2019-08-22 9:22 ` Cornelia Huck
2019-08-23 15:01 ` [Qemu-devel] [Qemu-trivial] " Laurent Vivier
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=a448f7da-c990-7dc5-e5ab-139994dfc814@redhat.com \
--to=philmd@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=tgfbeta@me.com \
/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).