staging: unisys: visorchipset: Use correct type for dev_no
authorJes Sorensen <Jes.Sorensen@redhat.com>
Mon, 13 Apr 2015 14:28:42 +0000 (10:28 -0400)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Thu, 30 Apr 2015 14:33:05 +0000 (16:33 +0200)
visorchipset_bus_info.dev_no is only assigned the value of
controlvm_message_packet.create_bus.dev_count, which is a u32. No
point promoting it to a u64.

Signed-off-by: Jes Sorensen <Jes.Sorensen@redhat.com>
Tested-by: Benjamin Romer <benjamin.romer@unisys.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/staging/unisys/visorchipset/visorchipset.h

index 3a8aa5614b4b29f897dd8e0d19d76c65d2fbbf38..3848de2533710c786e70d9d94b7f2430ce087b9c 100644 (file)
@@ -141,8 +141,7 @@ struct visorchipset_bus_info {
        struct controlvm_message_header pending_msg_hdr;/* CONTROLVM MsgHdr */
        /** For private use by the bus driver */
        void *bus_driver_context;
-       u64 dev_no;
-
+       u32 dev_no;
 };
 
 static inline struct visorchipset_bus_info *