From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752364AbdFSWbo (ORCPT ); Mon, 19 Jun 2017 18:31:44 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:57084 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751022AbdFSWbn (ORCPT ); Mon, 19 Jun 2017 18:31:43 -0400 Date: Mon, 19 Jun 2017 15:31:41 -0700 From: Andrew Morton To: Kees Cook Cc: Stephen Rothwell , LKML , Daniel Micay Subject: Re: [PATCH 0/7] CONFIG_FORTIFY_SOURCE Message-Id: <20170619153141.79bf647a48dbd2b93628cd71@linux-foundation.org> In-Reply-To: References: <1497903987-21002-1-git-send-email-keescook@chromium.org> <20170619145049.38dc14030059786ef6ca6a54@linux-foundation.org> X-Mailer: Sylpheed 3.4.1 (GTK+ 2.24.23; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 19 Jun 2017 15:12:22 -0700 Kees Cook wrote: > >> This was in my for-next/kspp tree, but since it depends on fixes in other > >> trees, the preference is for these to all get carried in -mm instead of > >> in KSPP. > > > > All the patches you sent are already in -next (from the kspp tree?) so > > I can't use them. > > Err... that's what you asked me to send? And I had removed them from > kspp so you could carry them. Oh, OK, I'll take a look later in the week after -next has caught up.