From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751494AbdFGJ2K (ORCPT ); Wed, 7 Jun 2017 05:28:10 -0400 Received: from foss.arm.com ([217.140.101.70]:57906 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751203AbdFGJ2I (ORCPT ); Wed, 7 Jun 2017 05:28:08 -0400 Date: Wed, 7 Jun 2017 10:27:21 +0100 From: Mark Rutland To: Kees Cook Cc: Ard Biesheuvel , Matt Fleming , Andrew Morton , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH 2/6] efi: Avoid fortify checks in EFI stub Message-ID: <20170607092720.GA29370@leverpostej> References: <1496724755-104187-1-git-send-email-keescook@chromium.org> <1496724755-104187-3-git-send-email-keescook@chromium.org> <20170606171712.GA4483@leverpostej> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 06, 2017 at 08:12:22PM -0700, Kees Cook wrote: > On Tue, Jun 6, 2017 at 10:17 AM, Mark Rutland wrote: > > Kees, as an aside, do you want me to patchify the vdso fixup? Or are > > you going to handle that? > > I sent that separately but discovered that my invocation of git > send-email failed to include a CC to you, even though I had it listed > as Suggested-by, etc. I think it's going to get queued for the arm64 > tree. Ah; great, thanks for handling that! FWIW, don't worry about the Cc. You're stuck between a rock and a hard place there, as git send-email only adds those with a "Cc: " line (ignoring all other tags), and some people don't want to be Cc'd after giving an ack, etc. Selfishly, one thing that would be helpful is to Cc LAKML on pathes for arm64. Myself and others will spot stuff that goes there, but don't subscribe to LKML (or scan it less frequently). Thanks, Mark.