summaryrefslogtreecommitdiff
path: root/tools/lib/python/kdoc/python_version.py
diff options
context:
space:
mode:
authorJakub Kicinski <kuba@kernel.org>2026-10-01 18:04:44 -0700
committerJakub Kicinski <kuba@kernel.org>2026-10-01 18:04:45 -0700
commit7efc07ad22c390289ec16dc676ac290a3827fac6 (patch)
treed8cfa5b8875aa3e754692ffd3a40511ccc346507 /tools/lib/python/kdoc/python_version.py
parent56fbbb662795b29f4d12a55cb1b456553a6ec3b0 (diff)
parentdb99b6fae21cfc09d7201b18470acbc01e45d038 (diff)
Merge branch 'eth-fbnic-update-bmc-mac-address-handling'
Alexander Duyck says: ==================== eth: fbnic: Update BMC MAC address handling Update the handling of BMC MAC addresses on fbnic, and in the process also address several issues identified with the changes. This patch series consists of 2 patches. The first patch addresses issues found in the bmc_present and bmc_tcam_reinit handling. It started out addressing the fact that present w/o a MAC address was flagged as an invalid message. However, we ended up also addressing a potential race in that setting bmc_present and need_bmc_tcam_reinit could potentially race against the bmc_rpc_check. To address that the bit flags were moved to a state bitmap and are now handled via the test_and_clear_bit and assign_bit operations. The second patch cleans up the BMC MAC addresses in the TCAMs if the BMC opts to disable the channel and the FW notifies us of the BMC removal. By doing this we can terminate the now defunct paths through our NIC data path to the BMC. Similarly with this a potential race was found due to recent changes that had moved the handling for the TCAMs out of the RTNL mutex and into the netdev instance lock. To maintain sync additional locking was added. ==================== Link: https://patch.msgid.link/179061185153.414394.13396934246780284806.stgit@ahduyck-xeon-server.home.arpa Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/lib/python/kdoc/python_version.py')
0 files changed, 0 insertions, 0 deletions