From: Jiri Pirko <jiri@resnulli.us>
To: sfeldma@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next 3/3] rocker: put port in FORWADING state after leaving bridge
Date: Thu, 26 Feb 2015 08:07:48 +0100 [thread overview]
Message-ID: <20150226070748.GD2074@nanopsycho.orion> (raw)
In-Reply-To: <1424924138-15928-4-git-send-email-sfeldma@gmail.com>
Thu, Feb 26, 2015 at 05:15:38AM CET, sfeldma@gmail.com wrote:
>From: Scott Feldman <sfeldma@gmail.com>
>
>Cleanup the port forwarding state transitions for the cases when the port
>joins or leaves a bridge, or is brought admin UP or DOWN. When port is
>bridged, we can rely on bridge driver putting port in correct state using
>STP callback into port driver, regardless if bridge is enabled for STP or not.
>When port is not bridged, we can reuse some of the STP code to enabled or
>disable forwarding depending on UP or DOWN.
>
>Tested by trying all the transitions from bridge/not bridge, and UP/DOWN, and
>verifying port is in the correct forwarding state after each transition.
>
>Signed-off-by: Scott Feldman <sfeldma@gmail.com>
Acked-by: Jiri Pirko <jiri@resnulli.us>
next prev parent reply other threads:[~2015-02-26 7:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 4:15 [PATCH net-next 0/3] rocker cleanups sfeldma
2015-02-26 4:15 ` [PATCH net-next 1/3] rocker: fix non-portable err return codes sfeldma
2015-02-26 6:50 ` Jiri Pirko
2015-02-26 12:17 ` David Laight
2015-02-26 14:04 ` Scott Feldman
2015-02-26 4:15 ` [PATCH net-next 2/3] rocker: rename lport to pport sfeldma
2015-02-26 6:55 ` Jiri Pirko
2015-02-26 4:15 ` [PATCH net-next 3/3] rocker: put port in FORWADING state after leaving bridge sfeldma
2015-02-26 7:07 ` Jiri Pirko [this message]
2015-02-26 16:22 ` [PATCH net-next 0/3] rocker cleanups 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=20150226070748.GD2074@nanopsycho.orion \
--to=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=sfeldma@gmail.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).