On Thu, May 05, 2016 at 04:56:43PM -0300, Thadeu Lima de Souza Cascardo wrote: > On Thu, May 05, 2016 at 09:31:41PM +0200, Jiri Benc wrote: > > On Thu, 5 May 2016 13:36:44 -0300, Thadeu Lima de Souza Cascardo wrote: > > > Use ARPHRD_VXLANGPE to identify VxLAN GPE interfaces. This is going to be > > > used > > > to allow GPE interfaces to be added as openvswitch ports. > > > > What's wrong with ARPHRD_NONE? I don't think we need a separate type > > for VXLAN-GPE. Just use ARPHRD_NONE in ovs and things should work, for > > all ARPHRD_NONE interfaces as a bonus. > > > > That's fine for me. I looked quickly at the few devices using ARPHRD_NONE in > upstream kernel, not sure if there are broken out-of-tree drivers out there. > And > should we care?
It seems unlikely to me that we should.
