summaryrefslogtreecommitdiff
path: root/net/ipv4/raw.c
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2020-08-24 18:01:33 -0700
committerDavid S. Miller <davem@davemloft.net>2020-08-24 18:01:33 -0700
commit0caeba3d3c1f08ecee4975d345858c19809475d7 (patch)
treeda9fe17aef47514c3715b1bfe55b54a9b22bf52a /net/ipv4/raw.c
parent9ab90179483350e516439795d38029dab2727520 (diff)
parentadc100d0988841c56dc5caebc3abec3871985b3a (diff)
downloadlwn-0caeba3d3c1f08ecee4975d345858c19809475d7.tar.gz
lwn-0caeba3d3c1f08ecee4975d345858c19809475d7.zip
Merge branch 'qed-introduce-devlink-health-support'
Igor Russkikh says: ==================== qed: introduce devlink health support This is a followup implementation after series https://patchwork.ozlabs.org/project/netdev/cover/20200514095727.1361-1-irusskikh@marvell.com/ This is an implementation of devlink health infrastructure. With this we are now able to report HW errors to devlink, and it'll take its own actions depending on user configuration to capture and store the dump at the bad moment, and to request the driver to recover the device. So far we do not differentiate global device failures or specific PCI function failures. This means that some errors specific to one physical function will affect an entire device. This is not yet fully designed and verified, will followup in future. Solution was verified with artificial HW errors generated, existing tools for dump analysis could be used. v7: comments from Jesse and Jakub - p2: extra edev check - p9: removed extra indents v6: patch 4: changing serial to board.serial and fw to fw.app v5: improved patch 4 description v4: - commit message and other fixes after Jiri's comments - removed one patch (will send to net) v3: fix uninit var usage in patch 11 v2: fix #include issue from kbuild test robot. ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/ipv4/raw.c')
0 files changed, 0 insertions, 0 deletions