All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Graf <tgraf@suug.ch>
To: Vlad Yasevich <vyasevic@redhat.com>
Cc: Jiri Pirko <jiri@resnulli.us>,
	netdev@vger.kernel.org, shemminger@vyatta.com,
	davem@davemloft.net, or.gerlitz@gmail.com, jhs@mojatatu.com,
	mst@redhat.com
Subject: Re: [PATCH V2 00/12] Add basic VLAN support to bridges
Date: Wed, 19 Dec 2012 17:20:55 +0000	[thread overview]
Message-ID: <20121219172055.GD6975@casper.infradead.org> (raw)
In-Reply-To: <50D1F551.6010301@redhat.com>

On 12/19/12 at 12:11pm, Vlad Yasevich wrote:
> Could we consolidate the code after this is accepted and all the parties
> can agree on the consolidation?  I'd really like to keep this series
> as minimally invasive as possible.

Sure, this was just a general remark on general future direction :)

  parent reply	other threads:[~2012-12-19 17:20 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-18 19:00 [PATCH V2 00/12] Add basic VLAN support to bridges Vlad Yasevich
2012-12-18 19:00 ` [PATCH V2 01/12] bridge: Add vlan filtering infrastructure Vlad Yasevich
2012-12-18 21:13   ` Eric Dumazet
2012-12-18 21:26     ` Vlad Yasevich
2012-12-18 19:00 ` [PATCH V2 02/12] bridge: Validate that vlan is permitted on ingress Vlad Yasevich
2012-12-18 19:00 ` [PATCH V2 03/12] bridge: Verify that a vlan is allowed to egress on give port Vlad Yasevich
2012-12-18 19:00 ` [PATCH V2 04/12] bridge: Cache vlan in the cb for faster egress lookup Vlad Yasevich
2012-12-18 19:00 ` [PATCH V2 05/12] bridge: Add vlan to unicast fdb entries Vlad Yasevich
2012-12-18 19:00 ` [PATCH V2 06/12] bridge: Add vlan id to multicast groups Vlad Yasevich
2012-12-18 19:00 ` [PATCH V2 07/12] bridge: Add netlink interface to configure vlans on bridge ports Vlad Yasevich
2012-12-18 19:00 ` [PATCH V2 08/12] bridge: Add vlan support to static neighbors Vlad Yasevich
2012-12-18 19:01 ` [PATCH V2 09/12] bridge: Add the ability to configure untagged vlans Vlad Yasevich
2012-12-18 23:01   ` Michael S. Tsirkin
2012-12-18 23:03     ` Vlad Yasevich
2012-12-18 23:10       ` Michael S. Tsirkin
2012-12-19 14:50         ` Vlad Yasevich
2012-12-18 23:04   ` Michael S. Tsirkin
2012-12-19  1:06     ` Vlad Yasevich
2012-12-18 19:01 ` [PATCH V2 10/12] bridge: Implement untagged vlan handling Vlad Yasevich
2012-12-18 19:01 ` [PATCH V2 11/12] bridge: Dump vlan information from a bridge port Vlad Yasevich
2012-12-18 19:01 ` [PATCH V2 12/12] bridge: Add vlan support for local fdb entries Vlad Yasevich
2012-12-18 22:32 ` [PATCH V2 00/12] Add basic VLAN support to bridges Jiri Pirko
2012-12-18 22:46   ` Vlad Yasevich
2012-12-19  8:27     ` Jiri Pirko
2012-12-19 16:25       ` Vlad Yasevich
2012-12-19 17:04       ` Thomas Graf
2012-12-19 17:11         ` Vlad Yasevich
2012-12-19 17:19           ` Jiri Pirko
2012-12-19 17:20           ` Thomas Graf [this message]
2012-12-19  8:10 ` Shmulik Ladkani
2012-12-19 14:13   ` Vlad Yasevich
2012-12-19 19:37     ` Shmulik Ladkani
2012-12-19 20:03       ` Vlad Yasevich
2012-12-19 22:59         ` Vlad Yasevich
2012-12-20  7:00         ` Shmulik Ladkani

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=20121219172055.GD6975@casper.infradead.org \
    --to=tgraf@suug.ch \
    --cc=davem@davemloft.net \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=or.gerlitz@gmail.com \
    --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 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.