Re: [PATCH 4.19 36/45] net/mlx5: Fix modify_cq_in alignment

2019-08-11 Thread Leon Romanovsky
On Sat, Aug 10, 2019 at 01:25:45PM +0200, Pavel Machek wrote: > Hi! > > > From: Edward Srouji > > > > [ Upstream commit 7a32f2962c56d9d8a836b4469855caeee8766bd4 ] > > > > Fix modify_cq_in alignment to match the device specification. > > After this fix the 'cq_umem_valid' field will be in the

Re: [PATCH 4.19 36/45] net/mlx5: Fix modify_cq_in alignment

2019-08-10 Thread Pavel Machek
Hi! > From: Edward Srouji > > [ Upstream commit 7a32f2962c56d9d8a836b4469855caeee8766bd4 ] > > Fix modify_cq_in alignment to match the device specification. > After this fix the 'cq_umem_valid' field will be in the right > offset. Is it neccessary for v4.19 stable? The cq_umem_valid field is

[PATCH 4.19 36/45] net/mlx5: Fix modify_cq_in alignment

2019-08-08 Thread Greg Kroah-Hartman
From: Edward Srouji [ Upstream commit 7a32f2962c56d9d8a836b4469855caeee8766bd4 ] Fix modify_cq_in alignment to match the device specification. After this fix the 'cq_umem_valid' field will be in the right offset. Cc: # 4.19 Fixes: bd37197554eb ("net/mlx5: Update mlx5_ifc with DEVX UID bits")