diff options
| author |   David S. Miller <davem@davemloft.net> | 2021-08-02 14:28:28 +0100 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2021-08-02 14:28:28 +0100 |
| commit | cebb5103f07e0924ff3e2a7feaf962d6f0c0aa88 (patch) | |
| tree | 62e520e3f8f56b520a361be5072b2ab9dd36f2f7 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | mhi: Fix networking tree build. (diff) | |
| parent | net: dsa: sja1105: match FDB entries regardless of inner/outer VLAN tag (diff) | |
| download | wireguard-linux-cebb5103f07e0924ff3e2a7feaf962d6f0c0aa88.tar.xz wireguard-linux-cebb5103f07e0924ff3e2a7feaf962d6f0c0aa88.zip | |
Merge branch 'sja1105-fdb-fixes'
Vladimir Oltean says:
====================
FDB fixes for NXP SJA1105
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
Patch 5/6 has a conflict with net-next (sorry), the commit message of
that patch describes how to deal with it. Thanks.
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions