From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754822Ab2KOVCt (ORCPT ); Thu, 15 Nov 2012 16:02:49 -0500 Received: from service87.mimecast.com ([91.220.42.44]:47677 "EHLO service87.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751358Ab2KOVCs convert rfc822-to-8bit (ORCPT ); Thu, 15 Nov 2012 16:02:48 -0500 Date: Thu, 15 Nov 2012 21:02:44 +0000 From: Will Deacon To: Kees Cook Cc: "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , Russell King , Geremy Condra , Catalin Marinas , Al Viro , Will Drewry Subject: Re: [PATCH v5 0/4] arch/arm: support seccomp Message-ID: <20121115210244.GB13998@mudshark.cambridge.arm.com> References: <1352587485-18348-1-git-send-email-keescook@chromium.org> <20121115132550.GA5570@mudshark.cambridge.arm.com> MIME-Version: 1.0 In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-OriginalArrivalTime: 15 Nov 2012 21:02:45.0133 (UTC) FILETIME=[8F4B93D0:01CDC374] X-MC-Unique: 112111521024603801 Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: 8BIT Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Nov 15, 2012 at 08:23:48PM +0000, Kees Cook wrote: > On Thu, Nov 15, 2012 at 5:25 AM, Will Deacon wrote: > > On Wed, Nov 14, 2012 at 07:07:13PM +0000, Kees Cook wrote: > >> Hi, any more thoughts on this series? I'd really like to get it into > >> -next. It's been running happily for a while now in the Chrome OS ARM > >> devices. > > > > I'm not familiar with seccomp in general, but the changes look ok now from > > an ARM point-of-view: > > > > Reviewed-by: Will Deacon > > > > These should probably go via Russell (who will put them into -next), so > > please send them to the patch system. > > Thanks. Is there a sensible way to send an ordered patch series to the > patch system? The Help doc says: > Please omit [PATCH] and other "useful" prefixes. > (and it wants the "KernelVersion: " in there too) > > Is there some way to indicate 1/4, 2/4, etc? If you're using git send-email, you don't need to do anything other than add a new tag below your S-o-B to indicate the kernel version, e.g: KernelVersion: 3.7-rc5 then send the patches (1 by 1 so they don't get re-ordered) to patches@arm.linux.org.uk You should receive a response indicating whether they were correctly formatted or not. Will