From: patchwork-bot+netdevbpf@kernel•org
To: Vladimir Oltean <vladimir.oltean@nxp•com>
Cc: netdev@vger•kernel.org, davem@davemloft•net, kuba@kernel•org,
andrew@lunn•ch, vivien.didelot@gmail•com, f.fainelli@gmail•com,
claudiu.manoil@nxp•com, alexandre.belloni@bootlin•com,
UNGLinuxDriver@microchip•com
Subject: Re: [PATCH v2 net-next] net: mscc: ocelot: fix incorrect balancing with down LAG ports
Date: Sat, 08 Jan 2022 03:10:10 +0000 [thread overview]
Message-ID: <164161141079.29029.4081900562686606337.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220107164332.402133-1-vladimir.oltean@nxp.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel•org>:
On Fri, 7 Jan 2022 18:43:32 +0200 you wrote:
> Assuming the test setup described here:
> https://patchwork.kernel.org/project/netdevbpf/cover/20210205130240.4072854-1-vladimir.oltean@nxp.com/
> (swp1 and swp2 are in bond0, and bond0 is in a bridge with swp0)
>
> it can be seen that when swp1 goes down (on either board A or B), then
> traffic that should go through that port isn't forwarded anywhere.
>
> [...]
Here is the summary with links:
- [v2,net-next] net: mscc: ocelot: fix incorrect balancing with down LAG ports
https://git.kernel.org/netdev/net-next/c/a14e6b69f393
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:[~2022-01-08 3:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 16:43 [PATCH v2 net-next] net: mscc: ocelot: fix incorrect balancing with down LAG ports Vladimir Oltean
2022-01-08 3:10 ` 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=164161141079.29029.4081900562686606337.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=UNGLinuxDriver@microchip$(echo .)com \
--cc=alexandre.belloni@bootlin$(echo .)com \
--cc=andrew@lunn$(echo .)ch \
--cc=claudiu.manoil@nxp$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=f.fainelli@gmail$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=vivien.didelot@gmail$(echo .)com \
--cc=vladimir.oltean@nxp$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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