From: Vlad Yasevich <vyasevic@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
mst@redhat.com
Subject: Re: [PATCHv4 net-next 0/2] Add two new flags to bridge.
Date: Tue, 30 Apr 2013 15:17:58 -0400 [thread overview]
Message-ID: <518018E6.3080601@redhat.com> (raw)
In-Reply-To: <20130430.151212.196427351152373468.davem@davemloft.net>
On 04/30/2013 03:12 PM, David Miller wrote:
> From: Vlad Yasevich <vyasevic@redhat.com>
> Date: Tue, 30 Apr 2013 14:18:45 -0400
>
>> 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.
>
> As per:
>
> http://marc.info/?l=linux-netdev&m=136730964130303&w=2
>
> It is absolutely, positively, not appropriate to submit new features
> at this time.
>
> If I can make my announcements more intelligable to you, please let me
> know how.
>
Sorry, missed it this morning...
-vlad
next prev parent reply other threads:[~2013-04-30 19:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 18:18 [PATCHv4 net-next 0/2] Add two new flags to bridge Vlad Yasevich
2013-04-30 18:18 ` [PATCHv4 net-next 1/2] bridge: Add flag to control mac learning Vlad Yasevich
2013-04-30 18:18 ` [PATCHv4 net-next 2/2] bridge: Add a flag to control unicast packet flood Vlad Yasevich
2013-04-30 19:41 ` Stephen Hemminger
2013-04-30 18:18 ` [PATCHv4 net-next 0/2] Add two new flags to bridge Vlad Yasevich
2013-04-30 19:12 ` David Miller
2013-04-30 19:17 ` Vlad Yasevich [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-06-05 14:07 Vlad Yasevich
2013-06-05 14:14 ` Sergei Shtylyov
2013-06-05 14:18 ` Vlad Yasevich
2013-06-11 9:05 ` 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=518018E6.3080601@redhat.com \
--to=vyasevic@redhat.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=mst@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).