From: Vlad Yasevich <vyasevic@redhat.com>
To: netdev@vger.kernel.org
Cc: shemminger@vyatta.com
Subject: Re: [PATCHv2 iproute2 0/3] Bridge VLAN support
Date: Wed, 06 Mar 2013 11:26:51 -0500 [thread overview]
Message-ID: <51376E4B.4060605@redhat.com> (raw)
In-Reply-To: <1362081846-25268-1-git-send-email-vyasevic@redhat.com>
On 02/28/2013 03:04 PM, Vlad Yasevich wrote:
> This series adds VLAN configuration to the bridge command. With this
> series, one can specify vlans in FDB entries as well as to configure
> VLAN configuration on the bridge ports.
>
Stephen
This wad resent after you reopened iproute2. Did you see it? Do you
have any further comments?
Thanks
-vlad
> Since v1:
> - Rebased.
> - Call rtnl_wilddump_req_filter from rtnl_wilddump_request. Preserve always
> setting the RTEXT_FILTER_VF filter.
>
> Vlad Yasevich (3):
> bridge: Add vlan support to fdb entries
> bridge: Add vlan configuration support
> bridge: Update bridge man pages to include vlan command
>
> bridge/Makefile | 2 +-
> bridge/br_common.h | 1 +
> bridge/bridge.c | 3 +-
> bridge/fdb.c | 16 ++++-
> bridge/vlan.c | 220 ++++++++++++++++++++++++++++++++++++++++++++++++++
> include/libnetlink.h | 2 +
> lib/libnetlink.c | 8 ++-
> man/man8/bridge.8 | 73 ++++++++++++++++-
> 8 files changed, 320 insertions(+), 5 deletions(-)
> create mode 100644 bridge/vlan.c
>
next prev parent reply other threads:[~2013-03-06 16:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 20:04 [PATCHv2 iproute2 0/3] Bridge VLAN support Vlad Yasevich
2013-02-28 20:04 ` [PATCHv2 iproute2 1/3] bridge: Add vlan support to fdb entries Vlad Yasevich
2013-02-28 20:04 ` [PATCHv2 iproute2 2/3] bridge: Add vlan configuration support Vlad Yasevich
2013-02-28 20:04 ` [PATCHv2 iproute2 3/3] bridge: Update bridge man pages to include vlan command Vlad Yasevich
2013-03-06 16:26 ` Vlad Yasevich [this message]
2013-03-06 19:06 ` [PATCHv2 iproute2 0/3] Bridge VLAN support Stephen Hemminger
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=51376E4B.4060605@redhat.com \
--to=vyasevic@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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).