From: David Miller <davem@davemloft.net>
To: jiri@resnulli.us
Cc: pabeni@redhat.com, netdev@vger.kernel.org, jiri@mellanox.com,
aduyck@mirantis.com, edumazet@google.com, daniel@iogearbox.net
Subject: Re: [PATCH net] net: avoid vlan ptype specific match to be leaked on real device
Date: Sun, 26 Jun 2016 16:06:08 -0400 (EDT) [thread overview]
Message-ID: <20160626.160608.2073563033978522175.davem@davemloft.net> (raw)
In-Reply-To: <20160622124050.GD2068@nanopsycho.orion>
From: Jiri Pirko <jiri@resnulli.us>
Date: Wed, 22 Jun 2016 14:40:50 +0200
> The patch only unified the behaviour so everyone know what to expect
> regardless of the device type.
+1
And reverting this behavior back is going to hurt more people than it
will help, so I am not going to apply this, sorry.
next prev parent reply other threads:[~2016-06-26 20:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 10:25 [PATCH net] net: avoid vlan ptype specific match to be leaked on real device Paolo Abeni
2016-06-22 10:55 ` Jiri Pirko
2016-06-22 12:21 ` Paolo Abeni
2016-06-22 12:40 ` Jiri Pirko
2016-06-26 20:06 ` David Miller [this message]
2016-06-27 9:28 ` Paolo Abeni
2016-06-27 9:37 ` Jiri Pirko
2016-06-27 13:43 ` David Miller
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=20160626.160608.2073563033978522175.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=aduyck@mirantis.com \
--cc=daniel@iogearbox.net \
--cc=edumazet@google.com \
--cc=jiri@mellanox.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).