On Tue, Nov 17, 2020 at 09:01:45AM +0200, Leon Romanovsky wrote: > From: Leon Romanovsky <leonro@xxxxxxxxxx> > > Changelog: > v5: > * Reorder patches to postpone changes in rdma_restrack_add to be in next series. > v4: https://lore.kernel.org/linux-rdma/20201104144008.3808124-1-leon@xxxxxxxxxx/ > * Rebased on latest for-upstream, all that time the patches were in > our regression and didn't introduce any issues. > * Took first five patches that hadn't any comments > v3: https://lore.kernel.org/lkml/20200926101938.2964394-1-leon@xxxxxxxxxx > * Rebased on already accepted patches. > * Added mlx4 special QPs to the list of not-tracked QPs (dropped previous mlx4 special QP patch). > * Separated to two patches change in return value of cma_listen_* routines. > * Changed commit messages and added Fixes as Jason requested. > v2: https://lore.kernel.org/linux-rdma/20200907122156.478360-1-leon@xxxxxxxxxx/ > * Added new patch to fix mlx4 failure on SR-IOV, it didn't have port set. > * Changed "RDMA/cma: Delete from restrack DB after successful destroy" patch. > v1: https://lore.kernel.org/lkml/20200830101436.108487-1-leon@xxxxxxxxxx > * Fixed rebase error, deleted second assignment of qp_type. > * Rebased code on latests rdma-next, the changes in cma.c caused to change > in patch "RDMA/cma: Delete from restrack DB after successful destroy". > * Dropped patch of port assignment, it is already done as part of this > series. > * I didn't add @calller description, regular users should not use _named() funciton. > v0: https://lore.kernel.org/lkml/20200824104415.1090901-1-leon@xxxxxxxxxx > > ---------------------------------------------------------------------------------- > > Leon Romanovsky (3): > RDMA/core: Track device memory MRs > RDMA/core: Allow drivers to disable restrack DB > RDMA/restrack: Support all QP types Applied to for-next, thanks Jason
