Re: [ovs-dev] [PATCH 1/3] ofp-parse: Separate fields properly.

2015-09-09 Thread Jesse Gross
On Tue, Sep 8, 2015 at 1:48 PM, Ben Pfaff wrote: > On Mon, Aug 31, 2015 at 07:57:04PM -0700, Jesse Gross wrote: >> Currently, each token in an OpenFlow match field is treated separately - >> whether this is a name, a value, or a single identifier. However, this >> means that attempting to get a va

Re: [ovs-dev] [PATCH 1/3] ofp-parse: Separate fields properly.

2015-09-08 Thread Ben Pfaff
On Mon, Aug 31, 2015 at 07:57:04PM -0700, Jesse Gross wrote: > Currently, each token in an OpenFlow match field is treated separately - > whether this is a name, a value, or a single identifier. However, this > means that attempting to get a value may result in grabbing the next > token if no value

[ovs-dev] [PATCH 1/3] ofp-parse: Separate fields properly.

2015-08-31 Thread Jesse Gross
Currently, each token in an OpenFlow match field is treated separately - whether this is a name, a value, or a single identifier. However, this means that attempting to get a value may result in grabbing the next token if no value exists. This avoids that problem by breaking the match string down i