From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Rothwell Subject: Re: linux-next: build failure after merge of the kspp tree Date: Mon, 19 Jun 2017 10:23:07 +1000 Message-ID: <20170619102307.32daa88d@canb.auug.org.au> References: <20170616113032.306720bf@canb.auug.org.au> <1497581467.17727.7.camel@gmail.com> <20170616133144.535aa23a@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20170616133144.535aa23a@canb.auug.org.au> Sender: linux-kernel-owner@vger.kernel.org To: Kees Cook Cc: Daniel Micay , Linux-Next Mailing List , Linux Kernel Mailing List , Andrew Morton List-Id: linux-next.vger.kernel.org Hi Stephen, On Fri, 16 Jun 2017 13:31:44 +1000 Stephen Rothwell wrote: > > Hi Kees, > > On Thu, 15 Jun 2017 20:20:47 -0700 Kees Cook wrote: > > > > I'm so confused -- isn't this in next? All the build tests I did were > > against yesterday's -next which includes this from what I can see... > > It is in next, but gets merged after the kspp tree ... so, this is when > inter-tree dependencies are a pain - I can merge the kspp tree later, > but then you have to remember which trees Linus must merge before you > send your pull request. That's why we like to have all trees be > effectively stand alone (as much as possible). OK, for now I have moved the merging of the kspp tree to after everything else (except Andrew's quilt series). This will (unfortunately) hide some dependencies between trees. -- Cheers, Stephen Rothwell