From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753062AbdFOPTt (ORCPT ); Thu, 15 Jun 2017 11:19:49 -0400 Received: from mail-it0-f43.google.com ([209.85.214.43]:36216 "EHLO mail-it0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751623AbdFOPTr (ORCPT ); Thu, 15 Jun 2017 11:19:47 -0400 MIME-Version: 1.0 In-Reply-To: <87k24dpzer.fsf@concordia.ellerman.id.au> References: <20170605170117.6a1fc15e@canb.auug.org.au> <20170615113548.3e4edcf4@canb.auug.org.au> <20170615120631.121c6c9b@canb.auug.org.au> <1497496709.1435.7.camel@gmail.com> <87k24dpzer.fsf@concordia.ellerman.id.au> From: Kees Cook Date: Thu, 15 Jun 2017 08:19:46 -0700 X-Google-Sender-Auth: TOUkcqbPUQvkz0kIVgOLdycBTkE Message-ID: Subject: Re: linux-next: build failure after merge of the akpm-current tree To: Michael Ellerman Cc: Daniel Micay , Stephen Rothwell , Andrew Morton , Linux-Next Mailing List , Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org ] On Wed, Jun 14, 2017 at 10:56 PM, Michael Ellerman wrote: > Daniel Micay writes: >> ... >> >> The arch mailing list was pinged about this which is how the powerpc >> folks got involved and fixed the issues there, including at least one >> runtime one. Not sure where (if anywhere) those are queued up, but Kees >> could pick those up too. > > I was expecting Kees to pick them up. Okay, cool. I'll get them into the kspp tree. -Kees -- Kees Cook Pixel Security