[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190723.112850.610952032088764951.davem@davemloft.net>
Date: Tue, 23 Jul 2019 11:28:50 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: leon@...nel.org
Cc: dledford@...hat.com, jgg@...lanox.com, edwards@...lanox.com,
linux-rdma@...r.kernel.org, yishaih@...lanox.com,
saeedm@...lanox.com, netdev@...r.kernel.org, leonro@...lanox.com
Subject: Re: [PATCH mlx5-next] net/mlx5: Fix modify_cq_in alignment
From: Leon Romanovsky <leon@...nel.org>
Date: Tue, 23 Jul 2019 10:12:55 +0300
> From: Edward Srouji <edwards@...lanox.com>
>
> 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: <stable@...r.kernel.org> # 4.19
> Fixes: bd37197554eb ("net/mlx5: Update mlx5_ifc with DEVX UID bits")
> Signed-off-by: Edward Srouji <edwards@...lanox.com>
> Reviewed-by: Yishai Hadas <yishaih@...lanox.com>
> Signed-off-by: Leon Romanovsky <leonro@...lanox.com>
Very confusing submission on many levels.
Coming from a Mellanox developer using a kernel.org email address.
Targetting the mlx5-next tree, yet CC:'ing stable.
A networking change, for which stable submissions are handled by me by
hand and not via CC:'ing stable.
Powered by blists - more mailing lists