From: David Miller <davem@davemloft.net>
To: sfeldma@gmail.com
Cc: netdev@vger.kernel.org, jiri@resnulli.us,
roopa@cumulusnetworks.com, vivien.didelot@savoirfairelinux.com,
ronen.arad@intel.com, f.fainelli@gmail.com
Subject: Re: [PATCH net-next 0/2] switchdev; add VLAN support for port's bridge_getlink
Date: Tue, 23 Jun 2015 06:57:42 -0700 (PDT) [thread overview]
Message-ID: <20150623.065742.1232677044170674438.davem@davemloft.net> (raw)
In-Reply-To: <1434958037-26057-1-git-send-email-sfeldma@gmail.com>
From: sfeldma@gmail.com
Date: Mon, 22 Jun 2015 00:27:15 -0700
> From: Scott Feldman <sfeldma@gmail.com>
>
> One more missing piece of the puzzle. Add vlan dump support to switchdev
> port's bridge_getlink. iproute2 "bridge vlan show" cmd already knows how
> to show the vlans installed on the bridge and the device , but (until now)
> no one implemented the port vlan part of the netlink PF_BRIDGE:RTM_GETLINK
> msg. Before this patch, "bridge vlan show":
...
> (When the port is bridged, the output repeats the vlan list for the vlans
> on the bridge side of the port and the vlans on the device side of the
> port. The listing above show no vlans for the device side even though they
> are installed).
>
> After this patch:
...
Series applied, thanks Scott.
prev parent reply other threads:[~2015-06-23 13:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 7:27 [PATCH net-next 0/2] switchdev; add VLAN support for port's bridge_getlink sfeldma
2015-06-22 7:27 ` [PATCH net-next 1/2] switchdev: rename vlan vid_start to vid_begin sfeldma
2015-06-22 7:27 ` [PATCH net-next 2/2] switchdev; add VLAN support for port's bridge_getlink sfeldma
2015-06-23 13:57 ` 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=20150623.065742.1232677044170674438.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=ronen.arad@intel.com \
--cc=roopa@cumulusnetworks.com \
--cc=sfeldma@gmail.com \
--cc=vivien.didelot@savoirfairelinux.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).