[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAGXu5j++TJ1uVhs3iWpPFrRtcOrpwdDXsH5Jb470Br9+id=9zg@mail.gmail.com>
Date: Mon, 19 Jun 2017 14:01:14 -0700
From: Kees Cook <keescook@...gle.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Daniel Micay <danielmicay@...il.com>,
Linux-Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: linux-next: build failure after merge of the kspp tree
On Sun, Jun 18, 2017 at 5:23 PM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi Stephen,
>
> On Fri, 16 Jun 2017 13:31:44 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>>
>> Hi Kees,
>>
>> On Thu, 15 Jun 2017 20:20:47 -0700 Kees Cook <keescook@...gle.com> 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.
In the other thread Andrew asked that I just have it all go through
-mm, so I've removed it from KSPP and sent the series his way (with
you in Cc).
Thanks!
-Kees
--
Kees Cook
Pixel Security
Powered by blists - more mailing lists