From 1b9cecdb88a18c2b5c173f04949577378d3d12b4 Mon Sep 17 00:00:00 2001 From: Keir Fraser Date: Fri, 2 Jul 2010 18:58:02 +0100 Subject: blktap2: make protocol specific usage of shared sring explicit I don't think protocol specific data really belongs in this header but since it is already there and we seem to be stuck with it let's at least make the users explicit lest people get caught out by future new fields moving the pad field around. This is the Xen portion of this change. The kernel portion will be sent separately. There is no dependency between the two. Signed-off-by: Ian Campbell Cc: Jeremy Fitzhardinge Cc: Daniel Stodden Cc: Dongxiao Xu --- tools/blktap2/drivers/tapdisk-vbd.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'tools/blktap2') diff --git a/tools/blktap2/drivers/tapdisk-vbd.c b/tools/blktap2/drivers/tapdisk-vbd.c index e6d18594ce..41425e2d83 100644 --- a/tools/blktap2/drivers/tapdisk-vbd.c +++ b/tools/blktap2/drivers/tapdisk-vbd.c @@ -1684,7 +1684,7 @@ tapdisk_vbd_check_ring_message(td_vbd_t *vbd) if (!vbd->ring.sring) return -EINVAL; - switch (vbd->ring.sring->pad[0]) { + switch (vbd->ring.sring->private.tapif_user.msg) { case 0: return 0; -- cgit v1.2.3