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 v10 net-next 00/12] VLAN filtering/VLAN aware bridge
Date: Wed, 13 Feb 2013 14:08:51 -0500 (EST) [thread overview]
Message-ID: <20130213.140851.2190933816965797127.davem@davemloft.net> (raw)
In-Reply-To: <1360777309-25522-1-git-send-email-vyasevic@redhat.com>
From: Vlad Yasevich <vyasevic@redhat.com>
Date: Wed, 13 Feb 2013 12:41:37 -0500
> Changes since v9:
> * series re-ordering so make functionality more distinct. Basic vlan
> filtering is patches 1-4. Support for PVID/untagged vlans is patches
> 5 and 6. VLAN support for FDB/MDB is patches 7-11. Patch 12 is
> still additional egress policy.
> * Slight simplification to code that extracts the VID from skb. Since we
> now depend on the vlan module, at the time of input skb_tci is guaranteed
> to be set if the packet had 8021q header. We can simply refere to it.
> * Changed the opaque 'parent' pointer from prior patches to a union so we
> can be much more explicit in our assignments.
> * Lots of additional testing with STP turned on. No issues were observed.
Thanks a lot for keeping this series uptodate Vlad.
Stephen, I think this series is ready, anything needed to be fixed still
can be follow-on patches. Agreed?
Thanks.
next prev parent reply other threads:[~2013-02-13 19:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 17:41 [PATCH v10 net-next 00/12] VLAN filtering/VLAN aware bridge Vlad Yasevich
2013-02-13 17:41 ` [PATCH v10 net-next 01/12] bridge: Add vlan filtering infrastructure Vlad Yasevich
2013-02-13 17:41 ` [PATCH v10 net-next 02/12] bridge: Validate that vlan is permitted on ingress Vlad Yasevich
2013-02-13 17:41 ` [PATCH v10 net-next 03/12] bridge: Verify that a vlan is allowed to egress on given port Vlad Yasevich
2013-02-13 17:41 ` [PATCH v10 net-next 04/12] bridge: Add netlink interface to configure vlans on bridge ports Vlad Yasevich
2013-02-13 17:41 ` [PATCH v10 net-next 05/12] bridge: Dump vlan information from a bridge port Vlad Yasevich
2013-02-13 17:41 ` [PATCH v10 net-next 06/12] bridge: Implement vlan ingress/egress policy with PVID Vlad Yasevich
2013-02-13 17:41 ` [PATCH v10 net-next 07/12] bridge: Add the ability to configure pvid Vlad Yasevich
2013-02-13 17:41 ` [PATCH v10 net-next 08/12] bridge: Add vlan to unicast fdb entries Vlad Yasevich
2013-02-13 17:41 ` [PATCH v10 net-next 09/12] bridge: Add vlan id to multicast groups Vlad Yasevich
2013-02-13 17:41 ` [PATCH v10 net-next 10/12] bridge: Add vlan support to static neighbors Vlad Yasevich
2013-02-13 19:25 ` Greg Rose
2013-02-13 17:41 ` [PATCH v10 net-next 11/12] bridge: Add vlan support for local fdb entries Vlad Yasevich
2013-02-13 17:41 ` [PATCH v10 net-next 12/12] bridge: Separate egress policy bitmap Vlad Yasevich
2013-02-13 19:08 ` David Miller [this message]
2013-02-13 19:43 ` [PATCH v10 net-next 00/12] VLAN filtering/VLAN aware bridge Vlad Yasevich
2013-02-13 19:48 ` David Miller
2013-02-13 20:14 ` [Bridge] " Jonathan Thibault
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.140851.2190933816965797127.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).