From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751955AbcJJAyF (ORCPT ); Sun, 9 Oct 2016 20:54:05 -0400 Received: from ozlabs.org ([103.22.144.67]:57999 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751710AbcJJAyD (ORCPT ); Sun, 9 Oct 2016 20:54:03 -0400 Date: Mon, 10 Oct 2016 11:54:01 +1100 From: Stephen Rothwell To: Doug Ledford Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Hariprasad Shenai , "David S. Miller" Subject: linux-next: manual merge of the rdma tree with Linus' tree Message-ID: <20161010115401.3ca0d3d3@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Doug, Today's linux-next merge of the rdma tree got a conflict in: drivers/net/ethernet/chelsio/cxgb4/cxgb4_main.c between commit: 0fbc81b3ad51 ("chcr/cxgb4i/cxgbit/RDMA/cxgb4: Allocate resources dynamically for all cxgb4 ULD's") from Linus' tree and commit: 086de575c142 ("cxgb4: advertise support for FR_NSMR_TPTE_WR") from the rdma tree. I fixed it up (the former removed the code modified by the latter) 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. -- Cheers, Stephen Rothwell