From: Thadeu Lima de Souza Cascardo <cascardo@redhat.com>
To: Jiri Benc <jbenc@redhat.com>
Cc: netdev@vger.kernel.org, Simon Horman <simon.horman@netronome.com>
Subject: Re: [PATCH net-next] vxlan: if_arp: introduce ARPHRD_VXLANGPE
Date: Thu, 5 May 2016 16:56:43 -0300 [thread overview]
Message-ID: <20160505195643.GA14919@indiana.gru.redhat.com> (raw)
In-Reply-To: <20160505213141.7ad29ebd@griffin>
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?
> > Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@redhat.com>
> > Cc: Jiri Benc <jbenc@redhat.com>
> > Cc: Simon Horman <simon.horman@netronome.com>
>
> You did not CC me nor Simon :-)
>
I am using sendemail.suppresscc=all to prevent some accidents. I am adding
confirm=always so I can double check before really sending.
Thanks.
Cascardo.
> Jiri
next prev parent reply other threads:[~2016-05-05 19:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-05 16:36 [PATCH net-next] vxlan: if_arp: introduce ARPHRD_VXLANGPE Thadeu Lima de Souza Cascardo
2016-05-05 19:31 ` Jiri Benc
2016-05-05 19:56 ` Thadeu Lima de Souza Cascardo [this message]
2016-05-06 8:11 ` Simon Horman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160505195643.GA14919@indiana.gru.redhat.com \
--to=cascardo@redhat.com \
--cc=jbenc@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=simon.horman@netronome.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).