From: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
To: Mike Manning <mmanning@vyatta.att-mail.com>,
netdev@vger.kernel.org, roopa@cumulusnetworks.com
Subject: Re: [PATCH net-next v3 2/5] vlan: do not transfer link state in vlan bridge binding mode
Date: Fri, 19 Apr 2019 14:51:56 +0300 [thread overview]
Message-ID: <bb55ee16-30cb-0f2d-e56d-0b4a3446277d@cumulusnetworks.com> (raw)
In-Reply-To: <20190418173535.22925-3-mmanning@vyatta.att-mail.com>
On 18/04/2019 20:35, Mike Manning wrote:
> In vlan bridge binding mode, the link state is no longer transferred
> from the lower device. Instead it is set by the bridge module according
> to the state of bridge ports that are members of the vlan.
>
> Signed-off-by: Mike Manning <mmanning@vyatta.att-mail.com>
> ---
> net/8021q/vlan.c | 18 ++++++++++++++----
> net/8021q/vlan_dev.c | 19 ++++++++++++-------
> 2 files changed, 26 insertions(+), 11 deletions(-)
>
Acked-by: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
next prev parent reply other threads:[~2019-04-19 19:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 17:35 [PATCH net-next v3 0/5] net: support binding vlan dev link state to vlan member bridge ports Mike Manning
2019-04-18 17:35 ` [PATCH net-next v3 1/5] vlan: support binding " Mike Manning
2019-04-19 11:51 ` Nikolay Aleksandrov
2019-04-18 17:35 ` [PATCH net-next v3 2/5] vlan: do not transfer link state in vlan bridge binding mode Mike Manning
2019-04-19 11:51 ` Nikolay Aleksandrov [this message]
2019-04-18 17:35 ` [PATCH net-next v3 3/5] bridge: support binding vlan dev link state to vlan member bridge ports Mike Manning
2019-04-19 11:54 ` Nikolay Aleksandrov
2019-04-18 17:35 ` [PATCH net-next v3 4/5] bridge: update vlan dev state when port added to or deleted from vlan Mike Manning
2019-04-19 11:55 ` Nikolay Aleksandrov
2019-04-18 17:35 ` [PATCH net-next v3 5/5] bridge: update vlan dev link state for bridge netdev changes Mike Manning
2019-04-19 11:59 ` Nikolay Aleksandrov
2019-04-19 12:01 ` [PATCH net-next v3 0/5] net: support binding vlan dev link state to vlan member bridge ports Nikolay Aleksandrov
2019-04-19 20:58 ` David Miller
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=bb55ee16-30cb-0f2d-e56d-0b4a3446277d@cumulusnetworks.com \
--to=nikolay@cumulusnetworks.com \
--cc=mmanning@vyatta.att-mail.com \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.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.