From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 56899C76190 for ; Tue, 23 Jul 2019 19:04:25 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 2FBDC2229A for ; Tue, 23 Jul 2019 19:04:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1563908665; bh=qBdiWSKWIjCsHen6DnbxUXpe6f7Z76IfupBI004rDYA=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=NYxGag89fhggvTAhaz2fR13BgpYJEL+5odm72FoCYSZ8cz7EovLOaJYqK0yKWfBvh 1Z4Gl71/rlHxeBGsGekARnqSpK3j755X07+dDDrXVYB/5H5FlrA83x1GepEfWPH9g1 2ewHJMtPX8jA1m1UpGd2ASCoVF2ssXDolry/l4Sg= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2391699AbfGWTEY (ORCPT ); Tue, 23 Jul 2019 15:04:24 -0400 Received: from mail.kernel.org ([198.145.29.99]:33130 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729511AbfGWTEX (ORCPT ); Tue, 23 Jul 2019 15:04:23 -0400 Received: from localhost (unknown [37.142.3.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 34A90218F0; Tue, 23 Jul 2019 19:04:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1563908662; bh=qBdiWSKWIjCsHen6DnbxUXpe6f7Z76IfupBI004rDYA=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=C556rVfU9yA8awMISWDNFXvi69SukXOZ/51Z7wszIOrAmvkAKrA6vrLUlfGyp809s noXnBRk//Ep/8rZoqEB2ATyLRt3aaVNL75nn/VSwqcDovIuiR9SxsQLOmbEseMqEXO 3ajYdU82gtgjVyI1emhn/2TfPOUBI7IS1RfkUgUw= Date: Tue, 23 Jul 2019 22:04:14 +0300 From: Leon Romanovsky To: David Miller Cc: dledford@redhat.com, jgg@mellanox.com, edwards@mellanox.com, linux-rdma@vger.kernel.org, yishaih@mellanox.com, saeedm@mellanox.com, netdev@vger.kernel.org Subject: Re: [PATCH mlx5-next] net/mlx5: Fix modify_cq_in alignment Message-ID: <20190723190414.GU5125@mtr-leonro.mtl.com> References: <20190723071255.6588-1-leon@kernel.org> <20190723.112850.610952032088764951.davem@davemloft.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190723.112850.610952032088764951.davem@davemloft.net> User-Agent: Mutt/1.12.0 (2019-05-25) Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Tue, Jul 23, 2019 at 11:28:50AM -0700, David Miller wrote: > From: Leon Romanovsky > Date: Tue, 23 Jul 2019 10:12:55 +0300 > > > From: Edward Srouji > > > > 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") > > Signed-off-by: Edward Srouji > > Reviewed-by: Yishai Hadas > > Signed-off-by: Leon Romanovsky > > Very confusing submission on many levels. > > Coming from a Mellanox developer using a kernel.org email address. It works for us and was proven internally as the best way to have setup which always works. > > Targetting the mlx5-next tree, yet CC:'ing stable. This patch was found by RDMA team, needed by RDMA but changes are located in code accessible by mlx5_core part. This is why mlx5-next. > > A networking change, for which stable submissions are handled by me by > hand and not via CC:'ing stable. The intention was to have this patch in shared mlx5 branch, which is picked by RDMA too. This "Cc: stable@..." together with merge through RDMA will ensure that such patch will be part of stable automatically. I can remove "Cc: ..." line if you think that it is inappropriate to have such line in patch in mlx5-next. Thanks