From: Maxime Bizon <mbizon@freebox.fr>
To: Jiri Pirko <jpirko@redhat.com>
Cc: John Fastabend <john.r.fastabend@intel.com>,
davem@davemloft.net, netdev@vger.kernel.org, jesse@nicira.com,
fubar@us.ibm.com
Subject: Re: [net-next PATCH] net: allow vlan traffic to be received under bond
Date: Thu, 13 Oct 2011 17:48:33 +0200 [thread overview]
Message-ID: <1318520913.9266.102.camel@sakura.staff.proxad.net> (raw)
In-Reply-To: <20111013153850.GA2031@minipsycho>
On Thu, 2011-10-13 at 17:38 +0200, Jiri Pirko wrote:
> Looks like it. The question is what is the correct behaviour...
since we don't want to break existing setup I would say the current one
but I must admit I'm not a big fan of it.
--
Maxime
next prev parent reply other threads:[~2011-10-13 15:48 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-10 19:16 [net-next PATCH] net: allow vlan traffic to be received under bond John Fastabend
2011-10-10 22:37 ` Jiri Pirko
2011-10-11 2:07 ` John Fastabend
2011-10-11 2:43 ` Jesse Gross
2011-10-11 11:08 ` Hans Schillstrom
2011-10-11 13:13 ` John Fastabend
2011-10-13 13:09 ` Hans Schillström
2011-10-11 13:16 ` John Fastabend
2011-10-11 10:57 ` Jiri Pirko
2011-10-13 15:04 ` Maxime Bizon
2011-10-13 15:38 ` Jiri Pirko
2011-10-13 15:48 ` Maxime Bizon [this message]
2011-10-13 15:59 ` Hans Schillström
2011-10-13 17:42 ` John Fastabend
2011-10-13 18:23 ` Hans Schillström
2011-10-14 0:22 ` Jesse Gross
2011-10-19 3:47 ` David Miller
2011-10-28 10:00 ` Eric Dumazet
2011-10-28 11:06 ` Eric Dumazet
2011-10-29 2:20 ` John Fastabend
2011-10-29 10:22 ` Eric Dumazet
2011-10-29 14:59 ` Jiri Pirko
2011-10-29 16:00 ` Eric Dumazet
2011-10-29 16:13 ` [PATCH v2] vlan: allow nested vlan_do_receive() Eric Dumazet
2011-10-29 16:28 ` Jiri Pirko
2011-10-30 8:38 ` Jiri Pirko
2011-10-30 8:44 ` David Miller
2011-10-30 8:44 ` Eric Dumazet
2011-10-29 16:16 ` [net-next PATCH] net: allow vlan traffic to be received under bond Jiri Pirko
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=1318520913.9266.102.camel@sakura.staff.proxad.net \
--to=mbizon@freebox.fr \
--cc=davem@davemloft.net \
--cc=fubar@us.ibm.com \
--cc=jesse@nicira.com \
--cc=john.r.fastabend@intel.com \
--cc=jpirko@redhat.com \
--cc=netdev@vger.kernel.org \
/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).