X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fopenvswitch%2Ftypes.h;h=90a32f55d7520702e298c35c09af62829e7508be;hb=7b9f1974f42d63693676d2611f9276fb8227e071;hp=9ddb85773fa283513b73cea49a7c5ca53c7e39f2;hpb=7bef2c918ac077da2156697ca821820e56561b9e;p=openvswitch diff --git a/include/openvswitch/types.h b/include/openvswitch/types.h index 9ddb8577..90a32f55 100644 --- a/include/openvswitch/types.h +++ b/include/openvswitch/types.h @@ -17,7 +17,7 @@ #ifndef OPENVSWITCH_TYPES_H #define OPENVSWITCH_TYPES_H 1 -#include +#include #include #include @@ -32,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.