On 26 May 2015 at 18:26, Ben Pfaff wrote:
> On Wed, May 20, 2015 at 02:53:22PM -0700, Joe Stringer wrote:
>> Figure out if a developer accidentally defines new NXM fields using an
>> existing number, and warn them. Useful particularly if new fields are
>> introduced upstream while rebasing an in-p
On Wed, May 20, 2015 at 02:53:22PM -0700, Joe Stringer wrote:
> Figure out if a developer accidentally defines new NXM fields using an
> existing number, and warn them. Useful particularly if new fields are
> introduced upstream while rebasing an in-progress patchset.
>
> Signed-off-by: Joe String
Figure out if a developer accidentally defines new NXM fields using an
existing number, and warn them. Useful particularly if new fields are
introduced upstream while rebasing an in-progress patchset.
Signed-off-by: Joe Stringer
---
v2: Don't modify oxm_name_to_class().
---
build-aux/extract-ofp
