diff options
| author | David S. Miller <davem@davemloft.net> | 2021-08-14 15:59:10 +0300 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2021-08-14 15:59:10 +0300 |
| commit | 2fa16787c47437318fc6ceeeddc34ceabd9313c7 (patch) | |
| tree | 4cefc1fb3e85246e3397dded87aa4df00d3dc9b7 /net/bridge/br_multicast.c | |
| parent | 38e3bfa86964961291760e7da6227794106d2247 (diff) | |
| parent | a1fcb106ae97cc34cc8101efafb89eaa837be009 (diff) | |
| download | linux-2fa16787c47437318fc6ceeeddc34ceabd9313c7.tar.xz | |
Merge branch 'devlink-cleanup-for-delay-event'
Leon Romanovsky says:
====================
Devlink cleanup for delay event series
Jakub's request to make sure that devlink events are delayed and not
printed till they fully accessible [1] requires us to implement delayed
event notification system in the devlink.
In order to do it, I moved some of my patches (xarray e.t.c) from the future
series to be before "Move devlink_register to be near devlink_reload_enable" [2].
That allows us to rely on DEVLINK_REGISTERED xarray mark to decide if to print
event or not.
Other patches are simple cleanup which is needed anyway.
[1] https://lore.kernel.org/lkml/20210811071817.4af5ab34@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com
[2] https://lore.kernel.org/lkml/cover.1628599239.git.leonro@nvidia.com
Next in the queue:
* Delay event series
* Move devlink_register to be near devlink_reload_enable"
* Extension of devlink_ops to be set dynamically
* devlink_reload_* delete
* Devlink locks rework to user xarray and reference counting
* ????
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/bridge/br_multicast.c')
0 files changed, 0 insertions, 0 deletions