From: David Miller <davem@davemloft.net>
To: vyasevic@redhat.com
Cc: netdev@vger.kernel.org, shemminger@vyatta.com,
bridge@lists.linux-foundation.org
Subject: Re: [PATCH v11 net-next 00/12] VLAN filtering/VLAN aware bridge
Date: Wed, 13 Feb 2013 20:10:57 -0500 (EST) [thread overview]
Message-ID: <20130213.201057.1655520092052468880.davem@davemloft.net> (raw)
In-Reply-To: <1360792820-14116-1-git-send-email-vyasevic@redhat.com>
From: Vlad Yasevich <vyasevic@redhat.com>
Date: Wed, 13 Feb 2013 17:00:08 -0500
> Vlad Yasevich (12):
> bridge: Add vlan filtering infrastructure
> bridge: Validate that vlan is permitted on ingress
> bridge: Verify that a vlan is allowed to egress on given port
> bridge: Add netlink interface to configure vlans on bridge ports
> bridge: Dump vlan information from a bridge port
> bridge: Implement vlan ingress/egress policy with PVID.
> bridge: Add the ability to configure pvid
> bridge: Add vlan to unicast fdb entries
> bridge: Add vlan id to multicast groups
> bridge: Add vlan support to static neighbors
> bridge: Add vlan support for local fdb entries
> bridge: Separate egress policy bitmap
Series applied, thanks Vlad.
prev parent reply other threads:[~2013-02-14 1:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 22:00 [PATCH v11 net-next 00/12] VLAN filtering/VLAN aware bridge Vlad Yasevich
2013-02-13 22:00 ` [PATCH v11 net-next 01/12] bridge: Add vlan filtering infrastructure Vlad Yasevich
2013-02-13 22:00 ` [PATCH v11 net-next 02/12] bridge: Validate that vlan is permitted on ingress Vlad Yasevich
2013-02-13 22:00 ` [PATCH v11 net-next 03/12] bridge: Verify that a vlan is allowed to egress on given port Vlad Yasevich
2013-02-13 22:00 ` [PATCH v11 net-next 04/12] bridge: Add netlink interface to configure vlans on bridge ports Vlad Yasevich
2013-02-13 22:00 ` [PATCH v11 net-next 05/12] bridge: Dump vlan information from a bridge port Vlad Yasevich
2013-02-13 22:00 ` [PATCH v11 net-next 06/12] bridge: Implement vlan ingress/egress policy with PVID Vlad Yasevich
2013-02-13 22:00 ` [PATCH v11 net-next 07/12] bridge: Add the ability to configure pvid Vlad Yasevich
2013-02-13 22:00 ` [PATCH v11 net-next 08/12] bridge: Add vlan to unicast fdb entries Vlad Yasevich
2013-02-13 22:00 ` [PATCH v11 net-next 09/12] bridge: Add vlan id to multicast groups Vlad Yasevich
2013-02-13 22:00 ` [PATCH v11 net-next 10/12] bridge: Add vlan support to static neighbors Vlad Yasevich
2013-02-13 22:10 ` Jitendra Kalsaria
2013-02-13 22:00 ` [PATCH v11 net-next 11/12] bridge: Add vlan support for local fdb entries Vlad Yasevich
2013-02-13 22:00 ` [PATCH v11 net-next 12/12] bridge: Separate egress policy bitmap Vlad Yasevich
2013-02-14 1:10 ` David Miller [this message]
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=20130213.201057.1655520092052468880.davem@davemloft.net \
--to=davem@davemloft.net \
--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).