From: John Snow <jsnow@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>, qemu-devel@nongnu.org
Cc: marc.mari.barcelo@gmail.com, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-2.7 0/8] libqos: use standard virtio headers
Date: Mon, 25 Apr 2016 15:09:14 -0400 [thread overview]
Message-ID: <571E6B5A.5070101@redhat.com> (raw)
In-Reply-To: <1461588373-26486-1-git-send-email-stefanha@redhat.com>
On 04/25/2016 08:46 AM, Stefan Hajnoczi wrote:
> This patch series eliminates code duplication in libqos virtio.
> include/standard-headers/ contains the Linux virtio header files so we don't
> need to define our own version of the structs and constants.
>
Is that a good idea? I had thought some of the intentional purpose of
duplicating the headers was to test the other versions.
> Stefan Hajnoczi (8):
> libqos: use virtio_ids.h for device ID definitions
> libqos: drop duplicated PCI vendor ID definition
> libqos: drop duplicated virtio_config.h definitions
> libqos: drop duplicated virtio_ring.h bit definitions
> libqos: drop duplicated virtio_vring.h structs
> libqos: drop duplicated virtio_blk.h definitions
> libqos: drop duplicated virtio_scsi.h definitions
> libqos: drop duplicated virtio_pci.h definitions
>
> tests/libqos/virtio-mmio.c | 5 +--
> tests/libqos/virtio-pci.c | 50 ++++++++++++++-------------
> tests/libqos/virtio-pci.h | 17 ---------
> tests/libqos/virtio.c | 42 +++++++++++-----------
> tests/libqos/virtio.h | 73 ++++-----------------------------------
> tests/virtio-blk-test.c | 86 ++++++++++++++++++++--------------------------
> tests/virtio-net-test.c | 10 +++---
> tests/virtio-scsi-test.c | 53 +++++++++++-----------------
> 8 files changed, 123 insertions(+), 213 deletions(-)
>
next prev parent reply other threads:[~2016-04-25 19:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 12:46 [Qemu-devel] [PATCH for-2.7 0/8] libqos: use standard virtio headers Stefan Hajnoczi
2016-04-25 12:46 ` [Qemu-devel] [PATCH for-2.7 1/8] libqos: use virtio_ids.h for device ID definitions Stefan Hajnoczi
2016-04-25 12:46 ` [Qemu-devel] [PATCH for-2.7 2/8] libqos: drop duplicated PCI vendor ID definition Stefan Hajnoczi
2016-04-25 12:46 ` [Qemu-devel] [PATCH for-2.7 3/8] libqos: drop duplicated virtio_config.h definitions Stefan Hajnoczi
2016-05-08 18:22 ` Marc Marí
2016-05-08 18:40 ` Marc Marí
2016-05-09 11:46 ` Stefan Hajnoczi
2016-04-25 12:46 ` [Qemu-devel] [PATCH for-2.7 4/8] libqos: drop duplicated virtio_ring.h bit definitions Stefan Hajnoczi
2016-04-25 12:46 ` [Qemu-devel] [PATCH for-2.7 5/8] libqos: drop duplicated virtio_vring.h structs Stefan Hajnoczi
2016-04-25 12:46 ` [Qemu-devel] [PATCH for-2.7 6/8] libqos: drop duplicated virtio_blk.h definitions Stefan Hajnoczi
2016-04-25 12:46 ` [Qemu-devel] [PATCH for-2.7 7/8] libqos: drop duplicated virtio_scsi.h definitions Stefan Hajnoczi
2016-04-25 12:46 ` [Qemu-devel] [PATCH for-2.7 8/8] libqos: drop duplicated virtio_pci.h definitions Stefan Hajnoczi
2016-04-25 19:09 ` John Snow [this message]
2016-04-26 9:58 ` [Qemu-devel] [PATCH for-2.7 0/8] libqos: use standard virtio headers Stefan Hajnoczi
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=571E6B5A.5070101@redhat.com \
--to=jsnow@redhat.com \
--cc=marc.mari.barcelo@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).