From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Lunn Subject: Re: linux-next: manual merge of the rdma tree with the net-next tree Date: Wed, 16 Mar 2016 22:15:03 +0100 Message-ID: <20160316211503.GA16382@lunn.ch> References: <20160316115809.61b4478e@canb.auug.org.au> <20160317075246.39a08e61@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from vps0.lunn.ch ([178.209.37.122]:48919 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755778AbcCPVPS (ORCPT ); Wed, 16 Mar 2016 17:15:18 -0400 Content-Disposition: inline In-Reply-To: <20160317075246.39a08e61@canb.auug.org.au> Sender: linux-next-owner@vger.kernel.org List-ID: To: Stephen Rothwell Cc: Linus Torvalds , Doug Ledford , David Miller , Network Development , linux-next , Linux Kernel Mailing List , Amir Vadai , Maor Gottlieb Hi Stephen > How about "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 want also want to Only the second want is required. > consider cooperate with the maintainer of the conflicting tree to cooperating Andrew