From: "Michael S. Tsirkin" <mst@redhat.com>
To: linux-kernel@vger.kernel.org,
Rusty Russell <rusty@rustcorp.com.au>,
virtualization@lists.linux-foundation.org
Cc: Rusty Russell <rusty@rustcorp.com.au>,
virtualization@lists.linux-foundation.org
Subject: [PATCH 3/6] tools/virtio: 64 bit features
Date: Mon, 15 Dec 2014 00:04:28 +0200 [thread overview]
Message-ID: <1418594542-22623-4-git-send-email-mst@redhat.com> (raw)
In-Reply-To: <1418594542-22623-1-git-send-email-mst@redhat.com>
Missed one place where vringh_test used
long to pass features. Fix it up to u64.
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
---
tools/virtio/vringh_test.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/virtio/vringh_test.c b/tools/virtio/vringh_test.c
index 13e0a76..51d922f 100644
--- a/tools/virtio/vringh_test.c
+++ b/tools/virtio/vringh_test.c
@@ -132,7 +132,7 @@ static inline int vringh_get_head(struct vringh *vrh, u16 *head)
return 1;
}
-static int parallel_test(unsigned long features,
+static int parallel_test(u64 features,
bool (*getrange)(struct vringh *vrh,
u64 addr, struct vringh_range *r),
bool fast_vringh)
--
MST
next prev parent reply other threads:[~2014-12-14 22:05 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
2014-12-14 22:04 ` [PATCH 2/6] tools/virtio: fix vringh test Michael S. Tsirkin
2014-12-14 22:04 ` Michael S. Tsirkin [this message]
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=1418594542-22623-4-git-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--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
all inboxes | Powered by JetHome®