qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: lvivier@redhat.com,
	Emanuele Giuseppe Esposito <e.emanuelegiuseppe@gmail.com>
Subject: Re: [Qemu-devel] [PATCH 1/5] tests/libqos: introduce virtio_start_device
Date: Fri, 18 Jan 2019 12:46:44 +0100	[thread overview]
Message-ID: <8caf272f-f229-c890-89e8-9e76882eb1e0@redhat.com> (raw)
In-Reply-To: <1547576349-13337-2-git-send-email-pbonzini@redhat.com>

On 2019-01-15 19:19, Paolo Bonzini wrote:
> From: Emanuele Giuseppe Esposito <e.emanuelegiuseppe@gmail.com>
> 
> This function is intended to group all the qvirtio_* functions that
> start the qvirtio devices.
> Applied in all tests using this combination of functions.
> 
> Signed-off-by: Emanuele Giuseppe Esposito <e.emanuelegiuseppe@gmail.com>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
[..]
> diff --git a/tests/virtio-blk-test.c b/tests/virtio-blk-test.c
> index 04c6087..f97c158 100644
> --- a/tests/virtio-blk-test.c
> +++ b/tests/virtio-blk-test.c
> @@ -116,10 +116,7 @@ static QVirtioPCIDevice *virtio_blk_pci_init(QPCIBus *bus, int slot)
>      g_assert_cmphex(dev->pdev->devfn, ==, ((slot << 3) | PCI_FN));
>  
>      qvirtio_pci_device_enable(dev);
> -    qvirtio_reset(&dev->vdev);
> -    qvirtio_set_acknowledge(&dev->vdev);
> -    qvirtio_set_driver(&dev->vdev);
> -
> +    qvirtio_start_device(&dev->vdev);
>      return dev;
>  }
>  
> @@ -333,6 +330,7 @@ static void pci_indirect(void)
>      qvirtio_set_features(&dev->vdev, features);
>  
>      vqpci = (QVirtQueuePCI *)qvirtqueue_setup(&dev->vdev, qs->alloc, 0);
> +
>      qvirtio_set_driver_ok(&dev->vdev);

Still unnecessary white-space change.

Apart from that nit, still:

Reviewed-by: Thomas Huth <thuth@redhat.com>

  parent reply	other threads:[~2019-01-18 11:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-15 18:19 [Qemu-devel] [PATCH 0/5] qtest driver framework (core only) Paolo Bonzini
2019-01-15 18:19 ` [Qemu-devel] [PATCH 1/5] tests/libqos: introduce virtio_start_device Paolo Bonzini
2019-01-16 17:16   ` Laurent Vivier
2019-01-18 11:46   ` Thomas Huth [this message]
2019-01-15 18:19 ` [Qemu-devel] [PATCH 2/5] tests/libqos: rename qpci_init_pc and qpci_init_spapr functions Paolo Bonzini
2019-01-16 19:55   ` Laurent Vivier
2019-01-18 12:23   ` Thomas Huth
2019-01-18 12:45     ` Paolo Bonzini
2019-01-15 18:19 ` [Qemu-devel] [PATCH 3/5] tests: remove rule for nonexisting qdev-monitor-test Paolo Bonzini
2019-01-16  5:43   ` Thomas Huth
2019-01-17  9:47   ` Laurent Vivier
2019-01-15 18:19 ` [Qemu-devel] [PATCH 4/5] tests/libqos: embed allocators instead of malloc-ing them separately Paolo Bonzini
2019-01-17 10:37   ` Laurent Vivier
2019-01-18 12:52   ` Thomas Huth
2019-01-18 12:59     ` Paolo Bonzini
2019-01-15 18:19 ` [Qemu-devel] [PATCH 5/5] tests: qgraph API for the qtest driver framework Paolo Bonzini
2019-01-18 16:39   ` Thomas Huth
2019-01-18 16:58     ` Eric Blake
2019-01-18 17:07     ` Paolo Bonzini

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=8caf272f-f229-c890-89e8-9e76882eb1e0@redhat.com \
    --to=thuth@redhat.com \
    --cc=e.emanuelegiuseppe@gmail.com \
    --cc=lvivier@redhat.com \
    --cc=pbonzini@redhat.com \
    --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).