X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;ds=sidebyside;f=include%2Fopenvswitch%2Ftypes.h;h=90a32f55d7520702e298c35c09af62829e7508be;hb=7b9f1974f42d63693676d2611f9276fb8227e071;hp=4d2a1e9a2f3a885a36dc406273a92b2d5048942c;hpb=805e8f4e2723cc0849bdb17fb81665ea4515fa45;p=openvswitch diff --git a/include/openvswitch/types.h b/include/openvswitch/types.h index 4d2a1e9a..90a32f55 100644 --- a/include/openvswitch/types.h +++ b/include/openvswitch/types.h @@ -17,6 +17,7 @@ #ifndef OPENVSWITCH_TYPES_H #define OPENVSWITCH_TYPES_H 1 +#include #include #include @@ -31,11 +32,12 @@ /* The ovs_be types indicate that an object is in big-endian, not * native-endian, byte order. They are otherwise equivalent to uint_t. * - * The OVS_BITWISE annotation allows the sparse checker to issue warnings - * for incorrect use of values in network byte order. */ -typedef uint16_t OVS_BITWISE ovs_be16; -typedef uint32_t OVS_BITWISE ovs_be32; -typedef uint64_t OVS_BITWISE ovs_be64; + * We bootstrap these from the Linux __be types. If we instead define our + * own independently then __be and ovs_be become mutually + * incompatible. */ +typedef __be16 ovs_be16; +typedef __be32 ovs_be32; +typedef __be64 ovs_be64; /* Netlink and OpenFlow both contain 64-bit values that are only guaranteed to * be aligned on 32-bit boundaries. These types help.