From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Rothwell Subject: Re: linux-next: build failure after merge of the akpm-current tree Date: Fri, 16 Jun 2017 11:20:19 +1000 Message-ID: <20170616112019.27a29a04@canb.auug.org.au> References: <20170605170117.6a1fc15e@canb.auug.org.au> <20170615113548.3e4edcf4@canb.auug.org.au> <20170615121220.4331a37b0fb736ec9da4e423@linux-foundation.org> <1497571513.17727.2.camel@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: Received: from ozlabs.org ([103.22.144.67]:52191 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751641AbdFPBUV (ORCPT ); Thu, 15 Jun 2017 21:20:21 -0400 In-Reply-To: Sender: linux-next-owner@vger.kernel.org List-ID: To: Kees Cook Cc: Daniel Micay , Andrew Morton , Linux-Next Mailing List , Linux Kernel Mailing List Hi Kees, On Thu, 15 Jun 2017 17:35:43 -0700 Kees Cook wrote: > > Sounds good. I've added ARCH_HAS_FORTIFY_SOURCE to the patch (and noted it). And that just made it in time for today's linux-next. I have removed the patches from Andrew's tree. -- Cheers, Stephen Rothwell