Jiri Pirko 7d7e9169a3 devlink: move devlink reload notifications back in between _down() and _up() calls ... This effectively reverts commit 05a7f4a8df ("devlink: Break parameter notification sequence to be before/after unload/load driver"). Cited commit resolved a problem in mlx5 params implementation, when param notification code accessed memory previously freed during reload. Now, when the params can be registered and unregistered when devlink instance is registered, mlx5 code unregisters the problematic param during devlink reload. The fix is therefore no longer needed. Current behavior is a it problematic, as it sends DEL notifications even in potential case when reload_down() call fails which might confuse userspace notifications listener. So move the reload notifications back where they were originally in between reload_down() and reload_up() calls. Signed-off-by: Jiri Pirko <jiri@nvidia.com> Reviewed-by: Jacob Keller <jacob.e.keller@intel.com> Signed-off-by: David S. Miller <davem@davemloft.net>		2023-01-30 08:37:46 +00:00
..
core.c	devlink: remove reporters_lock	2023-01-19 19:08:37 -08:00
devl_internal.h	netlink: fix spelling mistake in dump size assert	2023-01-24 16:29:11 -08:00
leftover.c	devlink: move devlink reload notifications back in between _down() and _up() calls	2023-01-30 08:37:46 +00:00
Makefile	devlink: split out netlink code	2023-01-05 22:13:39 -08:00
netlink.c	devlink: remove devlink_dump_for_each_instance_get() helper	2023-01-19 19:08:38 -08:00