On Thu, Nov 15, 2012 at 08:23:48PM +0000, Kees Cook wrote: > On Thu, Nov 15, 2012 at 5:25 AM, Will Deacon <[email protected]> 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 <[email protected]> > > > > 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 [email protected] You should receive a response indicating whether they were correctly formatted or not. Will -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
