From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Vlad Yasevich <vyasevic@redhat.com>
Cc: netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
shemminger@vyatta.com
Subject: Re: [PATCHv4 net-next 0/2] Add two new flags to bridge.
Date: Wed, 05 Jun 2013 18:14:11 +0400 [thread overview]
Message-ID: <51AF47B3.2070902@cogentembedded.com> (raw)
In-Reply-To: <1370441281-11281-1-git-send-email-vyasevic@redhat.com>
Hello.
On 05-06-2013 18:07, Vlad Yasevich wrote:
> The following series adds 2 new flags to bridge. One flag allows
> the user to control whether mac learning is performed on the interface
> or not. By default mac learning is on.
> The other flag allows the user to control whether unicast traffic
> is flooded (send without an fdb) to a given unicast port. Default is
> on.
> Changes since v4:
> - Implemented Stephen's suggestions.
> Changes since v2:
> - removed unused "unlock" tag.
> Changes since v1:
> - Integrated suggestion from MST to not impact RTM_NEWNEIGH and to
> skip lookups when learning is disabled.
> Vlad Yasevich (2):
> bridge: Add flag to control mac learning.
> bridge: Add a flag to control unicast packet flood.
> Vlad Yasevich (2):
> bridge: Add flag to control mac learning.
> bridge: Add a flag to control unicast packet flood.
Hm, why your patches are listed twice?
WBR, Sergei
next prev parent reply other threads:[~2013-06-05 14:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 14:07 [PATCHv4 net-next 0/2] Add two new flags to bridge Vlad Yasevich
2013-06-05 14:08 ` [PATCHv4 net-next 1/2] bridge: Add flag to control mac learning Vlad Yasevich
2013-06-05 14:08 ` [PATCHv4 net-next 2/2] bridge: Add a flag to control unicast packet flood Vlad Yasevich
2013-06-05 14:14 ` Sergei Shtylyov [this message]
2013-06-05 14:18 ` [PATCHv4 net-next 0/2] Add two new flags to bridge Vlad Yasevich
2013-06-11 9:05 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2013-04-30 18:18 Vlad Yasevich
2013-04-30 18:18 ` Vlad Yasevich
2013-04-30 19:12 ` David Miller
2013-04-30 19:17 ` Vlad Yasevich
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=51AF47B3.2070902@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=bridge@lists.linux-foundation.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
--cc=vyasevic@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).