aboutsummaryrefslogtreecommitdiffstats
path: root/scripts/bpf_helpers_doc.py
diff options
context:
space:
mode:
authorSaeed Mahameed <saeedm@mellanox.com>2020-02-21 21:45:58 +0000
committerDavid S. Miller <davem@davemloft.net>2020-02-21 15:41:10 -0800
commit4ae575661f98915410a90e11a27b7496e50df8cf (patch)
treed0023f52ce8af98795c8df28326b609b59d49947 /scripts/bpf_helpers_doc.py
parentMerge git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next (diff)
downloadlinux-dev-4ae575661f98915410a90e11a27b7496e50df8cf.tar.xz
linux-dev-4ae575661f98915410a90e11a27b7496e50df8cf.zip
net/mlxfw: Generic mlx FW flash status notify
FW flash status notify is currently implemented via a callback to the caller mlx module, and all it is doing is to call devlink_flash_update_status_notify with the specific module devlink instance. Instead of repeating the whole process for all mlx modules and re-implement the status_notify callback again and again. Just provide the devlink instance as part of mlxfw_dev when calling mlxfw_firmware_flash and let mlxfw do the devlink status updates directly. This will be very useful for adding status notify support to mlx5, as already done in this patch, with a simple one line of just providing the devlink instance to mlxfw_firmware_flash. mlxfw now depends on NET_DEVLINK as all other mlx modules. Signed-off-by: Saeed Mahameed <saeedm@mellanox.com> Reviewed-by: Ido Schimmel <idosch@mellanox.com> Acked-by: Jiri Pirko <jiri@mellanox.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'scripts/bpf_helpers_doc.py')
0 files changed, 0 insertions, 0 deletions