From: Rusty Russell <rusty@rustcorp.com.au>
To: "Michael S. Tsirkin" <mst@redhat.com>, linux-kernel@vger.kernel.org
Cc: David Hildenbrand <dahi@linux.vnet.ibm.com>,
Joel Stanley <joel@jms.id.au>,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH 1/6] tools/virtio: more stubs
Date: Fri, 19 Dec 2014 11:58:59 +1030 [thread overview]
Message-ID: <87ppbgsa04.fsf@rustcorp.com.au> (raw)
In-Reply-To: <1418594542-22623-2-git-send-email-mst@redhat.com>
"Michael S. Tsirkin" <mst@redhat.com> writes:
> As usual, add more stubs to fix test build after main
> codebase changes.
This doesn't apply, since:
> diff --git a/tools/virtio/linux/virtio_config.h b/tools/virtio/linux/virtio_config.h
> index dafe1c9..806d683 100644
> --- a/tools/virtio/linux/virtio_config.h
> +++ b/tools/virtio/linux/virtio_config.h
> @@ -1,8 +1,7 @@
> #include <linux/virtio_byteorder.h>
> #include <linux/virtio.h>
> +#include <uapi/linux/virtio_config.h>
>
> -#define VIRTIO_TRANSPORT_F_START 28
> -#define VIRTIO_TRANSPORT_F_END 32
> /*
Version in master has no headers in this file.
What's this based on?
Thanks,
Rusty.
next prev parent reply other threads:[~2014-12-19 1:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-14 22:04 [PATCH 0/6] virtio 1.0: tools update Michael S. Tsirkin
2014-12-14 22:04 ` [PATCH 1/6] tools/virtio: more stubs Michael S. Tsirkin
2014-12-19 1:28 ` Rusty Russell [this message]
2014-12-14 22:04 ` [PATCH 2/6] tools/virtio: fix vringh test Michael S. Tsirkin
2014-12-14 22:04 ` [PATCH 3/6] tools/virtio: 64 bit features Michael S. Tsirkin
2014-12-14 22:04 ` [PATCH 4/6] tools/virtio: enable -Werror Michael S. Tsirkin
2014-12-14 22:04 ` [PATCH 5/6] tools/virtio: add virtio 1.0 in virtio_test Michael S. Tsirkin
2014-12-14 22:04 ` [PATCH 6/6] tools/virtio: add virtio 1.0 in vringh_test Michael S. Tsirkin
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=87ppbgsa04.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=dahi@linux.vnet.ibm.com \
--cc=joel@jms.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=virtualization@lists.linux-foundation.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).