From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org, davem@davemloft.net,
andrew@lunn.ch, f.fainelli@gmail.com, vivien.didelot@gmail.com
Subject: Re: [PATCH net 0/6] FDB fixes for NXP SJA1105
Date: Mon, 02 Aug 2021 13:30:08 +0000 [thread overview]
Message-ID: <162791100876.19987.8798167357147623017.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210730171815.1773287-1-vladimir.oltean@nxp.com>
Hello:
This series was applied to netdev/net.git (refs/heads/master):
On Fri, 30 Jul 2021 20:18:09 +0300 you wrote:
> I have some upcoming patches that make heavy use of statically installed
> FDB entries, and when testing them on SJA1105P/Q/R/S and SJA1110, it
> became clear that these switches do not behave reliably at all.
>
> - On SJA1110, a static FDB entry cannot be installed at all
> - On SJA1105P/Q/R/S, it is very picky about the inner/outer VLAN type
> - Dynamically learned entries will make us not install static ones, or
> even if we do, they might not take effect
>
> [...]
Here is the summary with links:
- [net,1/6] net: dsa: sja1105: fix static FDB writes for SJA1110
https://git.kernel.org/netdev/net/c/cb81698fddbc
- [net,2/6] net: dsa: sja1105: overwrite dynamic FDB entries with static ones in .port_fdb_add
https://git.kernel.org/netdev/net/c/e11e865bf84e
- [net,3/6] net: dsa: sja1105: invalidate dynamic FDB entries learned concurrently with statically added ones
https://git.kernel.org/netdev/net/c/6c5fc159e092
- [net,4/6] net: dsa: sja1105: ignore the FDB entry for unknown multicast when adding a new address
https://git.kernel.org/netdev/net/c/728db843df88
- [net,5/6] net: dsa: sja1105: be stateless with FDB entries on SJA1105P/Q/R/S/SJA1110 too
https://git.kernel.org/netdev/net/c/589918df9322
- [net,6/6] net: dsa: sja1105: match FDB entries regardless of inner/outer VLAN tag
https://git.kernel.org/netdev/net/c/47c2c0c23121
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-08-02 13:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 17:18 [PATCH net 0/6] FDB fixes for NXP SJA1105 Vladimir Oltean
2021-07-30 17:18 ` [PATCH net 1/6] net: dsa: sja1105: fix static FDB writes for SJA1110 Vladimir Oltean
2021-07-30 17:18 ` [PATCH net 2/6] net: dsa: sja1105: overwrite dynamic FDB entries with static ones in .port_fdb_add Vladimir Oltean
2021-07-30 17:18 ` [PATCH net 3/6] net: dsa: sja1105: invalidate dynamic FDB entries learned concurrently with statically added ones Vladimir Oltean
2021-07-30 17:18 ` [PATCH net 4/6] net: dsa: sja1105: ignore the FDB entry for unknown multicast when adding a new address Vladimir Oltean
2021-07-30 17:18 ` [PATCH net 5/6] net: dsa: sja1105: be stateless with FDB entries on SJA1105P/Q/R/S/SJA1110 too Vladimir Oltean
2021-07-30 17:18 ` [PATCH net 6/6] net: dsa: sja1105: match FDB entries regardless of inner/outer VLAN tag Vladimir Oltean
2021-08-02 13:30 ` 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=162791100876.19987.8798167357147623017.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@gmail.com \
--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).