From: Stephen Hemminger <stephen@networkplumber.org>
To: Vlad Yasevich <vyasevic@redhat.com>
Cc: netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
mst@redhat.com
Subject: Re: [Bridge] [PATCHv4 net-next 2/2] bridge: Add a flag to control unicast packet flood.
Date: Tue, 30 Apr 2013 12:41:46 -0700 [thread overview]
Message-ID: <20130430124146.2091007d@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <1367345928-31135-3-git-send-email-vyasevic@redhat.com>
On Tue, 30 Apr 2013 14:18:47 -0400
Vlad Yasevich <vyasevic@redhat.com> wrote:
> + IFLA_BRPORT_UNICAST_FLOOD, /* control flood of unicast traffic */
Minor nit, comment could be just
/* flood unicast traffic */
and the comments for other flags line up, so why not make these line up?
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Hemminger <stephen@networkplumber.org>
To: Vlad Yasevich <vyasevic@redhat.com>
Cc: netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
mst@redhat.com
Subject: Re: [PATCHv4 net-next 2/2] bridge: Add a flag to control unicast packet flood.
Date: Tue, 30 Apr 2013 12:41:46 -0700 [thread overview]
Message-ID: <20130430124146.2091007d@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <1367345928-31135-3-git-send-email-vyasevic@redhat.com>
On Tue, 30 Apr 2013 14:18:47 -0400
Vlad Yasevich <vyasevic@redhat.com> wrote:
> + IFLA_BRPORT_UNICAST_FLOOD, /* control flood of unicast traffic */
Minor nit, comment could be just
/* flood unicast traffic */
and the comments for other flags line up, so why not make these line up?
next prev parent reply other threads:[~2013-04-30 19:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 18:18 [Bridge] [PATCHv4 net-next 0/2] Add two new flags to bridge Vlad Yasevich
2013-04-30 18:18 ` Vlad Yasevich
2013-04-30 18:18 ` [Bridge] [PATCHv4 net-next 1/2] bridge: Add flag to control mac learning Vlad Yasevich
2013-04-30 18:18 ` Vlad Yasevich
2013-04-30 18:18 ` [Bridge] [PATCHv4 net-next 2/2] bridge: Add a flag to control unicast packet flood Vlad Yasevich
2013-04-30 18:18 ` Vlad Yasevich
2013-04-30 19:41 ` Stephen Hemminger [this message]
2013-04-30 19:41 ` Stephen Hemminger
2013-04-30 18:18 ` [Bridge] [PATCHv4 net-next 0/2] Add two new flags to bridge Vlad Yasevich
2013-04-30 18:18 ` Vlad Yasevich
2013-04-30 19:12 ` [Bridge] " David Miller
2013-04-30 19:12 ` David Miller
2013-04-30 19:17 ` [Bridge] " Vlad Yasevich
2013-04-30 19:17 ` Vlad Yasevich
-- strict thread matches above, loose matches on Subject: below --
2013-06-05 14:07 [Bridge] " Vlad Yasevich
2013-06-05 14:08 ` [Bridge] [PATCHv4 net-next 2/2] bridge: Add a flag to control unicast packet flood 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=20130430124146.2091007d@nehalam.linuxnetplumber.net \
--to=stephen@networkplumber.org \
--cc=bridge@lists.linux-foundation.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.