Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp2565305ybb; Mon, 30 Mar 2020 08:36:06 -0700 (PDT) X-Google-Smtp-Source: ADFU+vthdJExgIhTmrvSbp8/kutvhtz+O/SkaSa3eqViG3nTd1sR7GLFqLHdtkV7zpk+qCEbsLoM X-Received: by 2002:a05:6830:1f5a:: with SMTP id u26mr9685065oth.208.1585582566144; Mon, 30 Mar 2020 08:36:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1585582566; cv=none; d=google.com; s=arc-20160816; b=h81dpWQslVhq9J3jDTh4qRv7QYcJWSCTtTxCdZsHnUZHdj1G2Af/CWLO6PtTAoqEZQ QD+w+X0zS5ycqm0/pyKrXpYIp9BRYn+6jVQ9+GtJOWYHKAaPjgu3MOj1bvxmDfYvHviw /MPtAg8R03PHw2/B36wB0+3YWD12ABVPl9ZYovY7QjqSkn1akgNlcPiNLxd1oO5wQBi2 PRolym6VY+Djyq5IWrTmEjSdYwmRF/tVSrh7XWT7rXMS5qcvEqjp1VWfXlvbPVJ5DEU+ symaUNkyI2aKxxrYNmGMqubKIYtDYZiSHUaXGVpITVRRMKfjHBvj0lFzttM1dM0dRICD s7QQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:from:references:to:subject:cc; bh=1a4xvrRfzDweQ/JYZQ70XYaKvcPK2wB/uWvl0R2A+88=; b=DA+Th5Bc+jNy7KvJgpYe0+Xmzg/HzKtCUXTZ8KcQKGDS7pF8Iw/8rYlml73SL3H2KC VP6uIz/ZTGyXN7vOEtfKhIoLM7ggcLT+No2iG1VFDXeJVDpp6ihWR6HyZvkIxTuGLTWX gJaFeOOpJYniCOKnhNNOcp76U3+Zvf3bYptWJ5KlMgExY4z5QmE6F9wcBzu4na9JTnoW jBYxHjsVAe0M/hwkXtK+qR5hq7z2r+izTvydtCl2pTZOIaTedT837F+bEJpr6gsN/TKm fiYyVZJCrBlAfRr6vUt0QbeHnpe30ldxw8ch/hB4/Ne2tZVgc1PWO4KDZTanZlKQiUky VmgQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x136si5833826oif.122.2020.03.30.08.35.45; Mon, 30 Mar 2020 08:36:06 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729005AbgC3PfV (ORCPT + 99 others); Mon, 30 Mar 2020 11:35:21 -0400 Received: from stargate.chelsio.com ([12.32.117.8]:26535 "EHLO stargate.chelsio.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728825AbgC3PfU (ORCPT ); Mon, 30 Mar 2020 11:35:20 -0400 Received: from [10.193.177.147] (lakshmi-pc.asicdesigners.com [10.193.177.147] (may be forged)) by stargate.chelsio.com (8.13.8/8.13.8) with ESMTP id 02UFYsPM025590; Mon, 30 Mar 2020 08:34:54 -0700 Cc: ayush.sawal@asicdesigners.com, Linux Crypto List , David Miller , Networking , Linux Next Mailing List , Linux Kernel Mailing List , Rohit Maheshwari Subject: Re: linux-next: manual merge of the crypto tree with the net-next tree To: Herbert Xu , Stephen Rothwell References: <20200330114209.1c7d5d11@canb.auug.org.au> <20200330004921.GA30111@gondor.apana.org.au> From: Ayush Sawal Message-ID: <81cc1934-16d1-0553-f280-83ecd097c0ee@chelsio.com> Date: Mon, 30 Mar 2020 21:05:26 +0530 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 MIME-Version: 1.0 In-Reply-To: <20200330004921.GA30111@gondor.apana.org.au> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Sender: linux-crypto-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org Hi Herbert, On 3/30/2020 6:19 AM, Herbert Xu wrote: > On Mon, Mar 30, 2020 at 11:42:09AM +1100, Stephen Rothwell wrote: >> Hi all, >> >> Today's linux-next merge of the crypto tree got a conflict in: >> >> drivers/crypto/chelsio/chcr_core.c >> >> between commit: >> >> 34aba2c45024 ("cxgb4/chcr : Register to tls add and del callback") >> >> from the net-next tree and commit: >> >> 53351bb96b6b ("crypto: chelsio/chcr - Fixes a deadlock between rtnl_lock and uld_mutex") >> >> from the crypto tree. >> >> I fixed it up (see below) and can carry the fix as necessary. This >> is now fixed as far as linux-next is concerned, but any non trivial >> conflicts should be mentioned to your upstream maintainer when your tree >> is submitted for merging. You may also want to consider cooperating >> with the maintainer of the conflicting tree to minimise any particularly >> complex conflicts. > Thanks for the heads up Stephen. > > Ayush, I'm going to drop the two chelsio patches. Going forward, > please send all chelsio patches via netdev. Ok, We will using netdev tree for sending all chelsio patches from now on. Thanks, Ayush