From: David Miller <davem@davemloft.net>
To: idosch@mellanox.com
Cc: netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
jiri@mellanox.com, petrm@mellanox.com,
nikolay@cumulusnetworks.com, stephen@networkplumber.org,
mlxsw@mellanox.com
Subject: Re: [PATCH net-next v2 0/6] mlxsw: SPAN: Support routes pointing at bridges
Date: Fri, 27 Apr 2018 20:28:00 -0400 (EDT) [thread overview]
Message-ID: <20180427.202800.1778798756850411051.davem@davemloft.net> (raw)
In-Reply-To: <20180427151111.22099-1-idosch@mellanox.com>
From: Ido Schimmel <idosch@mellanox.com>
Date: Fri, 27 Apr 2018 18:11:05 +0300
> Changes from v1 to v2:
>
> - Change the suite of bridge accessor functions to br_vlan_pvid_rtnl(),
> br_vlan_info_rtnl(), br_fdb_find_port_rtnl().
Please address Stephen Hemminger's feedback, otherwise this series
looks good to go.
Thanks.
prev parent reply other threads:[~2018-04-28 0:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 15:11 [PATCH net-next v2 0/6] mlxsw: SPAN: Support routes pointing at bridges Ido Schimmel
2018-04-27 15:11 ` [PATCH net-next v2 1/6] net: bridge: Publish bridge accessor functions Ido Schimmel
2018-04-27 15:38 ` Nikolay Aleksandrov
2018-04-27 16:08 ` Petr Machata
2018-04-27 16:11 ` Nikolay Aleksandrov
2018-04-27 16:28 ` Stephen Hemminger
2018-04-27 16:36 ` Petr Machata
2018-04-27 15:11 ` [PATCH net-next v2 2/6] mlxsw: spectrum: Extract mlxsw_sp_stp_spms_state() Ido Schimmel
2018-04-27 15:11 ` [PATCH net-next v2 3/6] mlxsw: spectrum_switchdev: Publish two functions Ido Schimmel
2018-04-27 15:11 ` [PATCH net-next v2 4/6] mlxsw: spectrum: Register SPAN before switchdev Ido Schimmel
2018-04-27 15:11 ` [PATCH net-next v2 5/6] mlxsw: Respin SPAN on switchdev events Ido Schimmel
2018-04-27 15:11 ` [PATCH net-next v2 6/6] mlxsw: spectrum_span: Allow bridge for gretap mirror Ido Schimmel
2018-04-27 15:39 ` Nikolay Aleksandrov
2018-04-28 0:28 ` 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=20180427.202800.1778798756850411051.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bridge@lists.linux-foundation.org \
--cc=idosch@mellanox.com \
--cc=jiri@mellanox.com \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=petrm@mellanox.com \
--cc=stephen@networkplumber.org \
/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).