On Wed, Jul 2, 2014 at 4:46 PM, Thomas Graf wrote:
> On 07/01/14 at 05:43pm, Jesse Gross wrote:
>> There are many possible ways that a flow can be invalid so we've
>> added logging for most of them. This adds logs for the remaining
>> possible cases so there isn't any ambiguity while debugging.
>>
On 07/01/14 at 05:43pm, Jesse Gross wrote:
> There are many possible ways that a flow can be invalid so we've
> added logging for most of them. This adds logs for the remaining
> possible cases so there isn't any ambiguity while debugging.
>
> CC: Federico Iezzi
> Signed-off-by: Jesse Gross
LGT
On 07/01/14 at 05:43pm, Jesse Gross wrote:
> There are many possible ways that a flow can be invalid so we've
> added logging for most of them. This adds logs for the remaining
> possible cases so there isn't any ambiguity while debugging.
>
> CC: Federico Iezzi
> Signed-off-by: Jesse Gross
It'
On Tue, Jul 01, 2014 at 05:43:39PM -0700, Jesse Gross wrote:
> There are many possible ways that a flow can be invalid so we've
> added logging for most of them. This adds logs for the remaining
> possible cases so there isn't any ambiguity while debugging.
>
> CC: Federico Iezzi
> Signed-off-by:
There are many possible ways that a flow can be invalid so we've
added logging for most of them. This adds logs for the remaining
possible cases so there isn't any ambiguity while debugging.
CC: Federico Iezzi
Signed-off-by: Jesse Gross
---
datapath/datapath.c | 12 +---
datapath/fl
