> On May 10, 2016, at 1:44 PM, Joe Stringer wrote:
>
> On 3 May 2016 at 18:31, Justin Pettit wrote:
>> Commit f2d105b5 (ofproto-dpif-xlate: xlate ct_{mark, label} correctly.)
>> introduced the ovs_u128_and() function. It directly takes ovs_u128
>> values as arguments instead of pointers to the
On 3 May 2016 at 18:31, Justin Pettit wrote:
> Commit f2d105b5 (ofproto-dpif-xlate: xlate ct_{mark, label} correctly.)
> introduced the ovs_u128_and() function. It directly takes ovs_u128
> values as arguments instead of pointers to them. As this is a bit more
> direct way to deal with 128-bit v
Commit f2d105b5 (ofproto-dpif-xlate: xlate ct_{mark, label} correctly.)
introduced the ovs_u128_and() function. It directly takes ovs_u128
values as arguments instead of pointers to them. As this is a bit more
direct way to deal with 128-bit values, modify the other utility
functions to do the sa
