diff options
| author |   David S. Miller <davem@davemloft.net> | 2021-08-18 10:48:52 +0100 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2021-08-18 10:48:52 +0100 |
| commit | 97712f8f912fb7f2e305468047421bcac0f6653c (patch) | |
| tree | 1a5b3fef53e35703f3c8cdc1a1f927508b5092fe /net/openvswitch/vport.c | |
| parent | net: dsa: sja1105: fix use-after-free after calling of_find_compatible_node, or worse (diff) | |
| parent | net: mdio-mux: Handle -EPROBE_DEFER correctly (diff) | |
| download | linux-dev-97712f8f912fb7f2e305468047421bcac0f6653c.tar.xz linux-dev-97712f8f912fb7f2e305468047421bcac0f6653c.zip | |
Merge branch 'mdio-fixes'
Saravana Kannan says:
====================
Clean up and fix error handling in mdio_mux_init()
This patch series was started due to -EPROBE_DEFER not being handled
correctly in mdio_mux_init() and causing issues [1]. While at it, I also
did some more error handling fixes and clean ups. The -EPROBE_DEFER fix is
the last patch.
Ideally, in the last patch we'd treat any error similar to -EPROBE_DEFER
but I'm not sure if it'll break any board/platforms where some child
mdiobus never successfully registers. If we treated all errors similar to
-EPROBE_DEFER, then none of the child mdiobus will work and that might be a
regression. If people are sure this is not a real case, then I can fix up
the last patch to always fail the entire mdio-mux init if any of the child
mdiobus registration fails.
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/openvswitch/vport.c')
0 files changed, 0 insertions, 0 deletions