From: patchwork-bot+netdevbpf@kernel.org
To: Colin Foster <colin.foster@in-advantage.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
vladimir.oltean@nxp.com, claudiu.manoil@nxp.com,
alexandre.belloni@bootlin.com, UNGLinuxDriver@microchip.com,
davem@davemloft.net, kuba@kernel.org
Subject: Re: [PATCH v1 net 0/1] net: mscc: ocelot: broadcast storm fixup
Date: Thu, 23 Sep 2021 12:20:07 +0000 [thread overview]
Message-ID: <163239960791.10392.14381330842241900586.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210923020338.1945812-1-colin.foster@in-advantage.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Wed, 22 Sep 2021 19:03:37 -0700 you wrote:
> Ocelot ports would still forward out ethernet broadcasts when they were
> in the LEARNING or BLOCKING state. This is due to the
> ocelot_get_bridge_fwd_mask, which would tell disabled ports to forward
> packets out all FORWARDING ports. Broadcast storms would insue.
>
> This patch restores the functionality of disabling forwarding for ports
> that aren't in the FORWARDING state. No more broadcast storms.
>
> [...]
Here is the summary with links:
- [v1,net,1/1] net: mscc: ocelot: fix forwarding from BLOCKING ports remaining enabled
https://git.kernel.org/netdev/net/c/acc64f52afac
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-09-23 12:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-23 2:03 [PATCH v1 net 0/1] net: mscc: ocelot: broadcast storm fixup Colin Foster
2021-09-23 2:03 ` [PATCH v1 net 1/1] net: mscc: ocelot: fix forwarding from BLOCKING ports remaining enabled Colin Foster
2021-09-23 12:20 ` patchwork-bot+netdevbpf [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=163239960791.10392.14381330842241900586.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.manoil@nxp.com \
--cc=colin.foster@in-advantage.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vladimir.oltean@nxp.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).