On Wed, 29 Sep 2021 15:00:41 +0300 Leon Romanovsky wrote: > This series starts from the fixing the bug introduced by implementing > devlink delayed notifications logic, where I missed some of the > notifications functions. > > The rest series provides a way to dynamically set devlink ops that is > needed for mlx5 multiport device and starts cleanup by removing > not-needed logic. > > In the next series, we will delete various publish API, drop general > lock, annotate the code and rework logic around devlink->lock. > > All this is possible because driver initialization is separated from the > user input now. Swapping ops is a nasty hack in my book. And all that to avoid having two op structures in one driver. Or to avoid having counters which are always 0? Sorry, at the very least you need better explanation for this.
