From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753990AbdGNMDy (ORCPT ); Fri, 14 Jul 2017 08:03:54 -0400 Received: from mx1.redhat.com ([209.132.183.28]:47772 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753472AbdGNMDw (ORCPT ); Fri, 14 Jul 2017 08:03:52 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com E9BFB2DE3C Authentication-Results: ext-mx09.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx09.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=dledford@redhat.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com E9BFB2DE3C Message-ID: <1500033829.2936.16.camel@redhat.com> Subject: Re: linux-next: manual merge of the rdma tree with Linus' tree From: Doug Ledford To: Leon Romanovsky , Stephen Rothwell Cc: Linux-Next Mailing List , Linux Kernel Mailing List , Daniel Jurgens , Paul Moore , Parav Pandit , Eli Cohen Date: Fri, 14 Jul 2017 08:03:49 -0400 In-Reply-To: <20170714045546.GV1528@mtr-leonro.local> References: <20170714111437.69a6b100@canb.auug.org.au> <1499995033.2936.12.camel@redhat.com> <20170714033416.GS1528@mtr-leonro.local> <20170714135018.5c849c1c@canb.auug.org.au> <20170714045546.GV1528@mtr-leonro.local> Organization: Red Hat, Inc. Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.38]); Fri, 14 Jul 2017 12:03:52 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2017-07-14 at 07:55 +0300, Leon Romanovsky wrote: > On Fri, Jul 14, 2017 at 01:50:26PM +1000, Stephen Rothwell wrote: > > Hi all, > > > > On Fri, 14 Jul 2017 06:34:16 +0300 Leon Romanovsky > > wrote: > > > > > > Sorry Doug, but it is not expected at all for the code which will > > > go to 4.14. > > > > > > Both patches in question were targeted for 4.13 and you was > > > expected to > > > see the merge conflicts during last month or so, prior to merge > > > window of 4.13. > > > > > > In 4.14, you should base your tree on Linus's tree and don't have > > > ANY > > > conflicts in your subsystem, between ANY subsystems and > > > especially > > > Linus, so we will be able to develop and test. > > > > > > For me, this merge conflict puts a large sign, that your tree is > > > not ready for 4.14. > > > > > > Please base your tree on Linus's tree. > > > > And if these commits are destined for v4.14, then they should not > > have > > been in linux-next yet. > > See, this announcement, > http://marc.info/?l=linux-rdma&m=149980130008834&w=2 Yes, and the patch in question is one of the many that I pulled out as fixes that I would end up submitting during the -rc cycle. Hence why I put the for-next tag on it. -- Doug Ledford GPG KeyID: B826A3330E572FDD Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD