From: David Miller <davem@davemloft.net>
To: nikolay@cumulusnetworks.com
Cc: netdev@vger.kernel.org, stephen@networkplumber.org,
herbert@gondor.apana.org.au, sashok@cumulusnetworks.com
Subject: Re: [PATCH net-next v2] bridge: multicast: start querier timer when running user-space stp
Date: Tue, 23 Jun 2015 03:31:02 -0700 (PDT) [thread overview]
Message-ID: <20150623.033102.2148484981874714822.davem@davemloft.net> (raw)
In-Reply-To: <1434703550-29305-1-git-send-email-nikolay@cumulusnetworks.com>
From: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
Date: Fri, 19 Jun 2015 01:45:50 -0700
> When STP is running in user-space and querier is configured, the
> querier timer is not started when a port goes to a non-blocking state.
> This patch unifies the user- and kernel-space stp multicast port enable
> path and enables it in all states different from blocking. Note that when a
> port goes in BR_STATE_DISABLED it's not enabled because that is handled
> in the beginning of the port list loop.
>
> Signed-off-by: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
> ---
> v2: Repurposed for net-next and implemented Herbert's suggestion for
> unifying both user- and kernel-space multicast enable port paths.
Applied.
prev parent reply other threads:[~2015-06-23 10:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 8:45 [PATCH net-next v2] bridge: multicast: start querier timer when running user-space stp Nikolay Aleksandrov
2015-06-19 13:47 ` Herbert Xu
2015-06-19 13:51 ` Nikolay Aleksandrov
2015-06-22 20:12 ` [PATCH net-next] bridge: multicast: disable port when in blocking state Nikolay Aleksandrov
2015-06-22 20:25 ` Nikolay Aleksandrov
2015-06-22 20:38 ` Nikolay Aleksandrov
2015-06-22 23:52 ` Herbert Xu
2015-06-23 10:26 ` Nikolay Aleksandrov
2015-06-23 11:47 ` [PATCH net-next] bridge: multicast: add a comment to br_port_state_selection about " Nikolay Aleksandrov
2015-06-23 13:26 ` Herbert Xu
2015-06-23 10:31 ` 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.033102.2148484981874714822.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=sashok@cumulusnetworks.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).