From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752470AbcFIWoF (ORCPT ); Thu, 9 Jun 2016 18:44:05 -0400 Received: from mail-pf0-f172.google.com ([209.85.192.172]:32780 "EHLO mail-pf0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751973AbcFIWnv (ORCPT ); Thu, 9 Jun 2016 18:43:51 -0400 From: Kevin Hilman To: Stephen Rothwell Cc: linux-next@vger.kernel.org, lkml , Neil Armstrong , Philipp Zabel Subject: Re: linux-next: build failure after merge of the amlogic tree Organization: BayLibre References: <20160606095559.67cf4f00@canb.auug.org.au> <20160606140231.394f5db7@canb.auug.org.au> Date: Thu, 09 Jun 2016 15:43:48 -0700 In-Reply-To: <20160606140231.394f5db7@canb.auug.org.au> (Stephen Rothwell's message of "Mon, 6 Jun 2016 14:02:31 +1000") Message-ID: <7hziquc7a3.fsf@baylibre.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Stephen Rothwell writes: > Hi Kevin, > > On Sun, 5 Jun 2016 20:40:28 -0700 Kevin Hilman wrote: >> >> Not forgotten, but merged through Philip's reset tree, which I thought >> was already in linux-next. Sorry about that. > > It may well be, but we dislike implicit dependencies between trees ... > it makes the merge order matter :-( What you should have is a common > non-rebasing branch that both trees merge. Yup, I'll work this out with Philipp. Kevin