Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757990Ab1F3Bbi (ORCPT ); Wed, 29 Jun 2011 21:31:38 -0400 Received: from tundra.namei.org ([65.99.196.166]:57993 "EHLO tundra.namei.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753661Ab1F3Bbc (ORCPT ); Wed, 29 Jun 2011 21:31:32 -0400 Date: Thu, 30 Jun 2011 11:30:42 +1000 (EST) From: James Morris To: Will Drewry cc: Chris Evans , linux-kernel@vger.kernel.org, Linus Torvalds , djm@mindrot.org, segoon@openwall.com, kees.cook@canonical.com, Ingo Molnar , rostedt@goodmis.org, fweisbec@gmail.com, tglx@linutronix.de, Randy Dunlap , linux-doc@vger.kernel.org, Eric Paris , linux-security-module@vger.kernel.org Subject: Re: [PATCH v9 05/13] seccomp_filter: Document what seccomp_filter is and how it works. In-Reply-To: Message-ID: References: <1308875813-20122-1-git-send-email-wad@chromium.org> <1308875813-20122-5-git-send-email-wad@chromium.org> User-Agent: Alpine 2.00 (LRH 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 785 Lines: 20 On Wed, 29 Jun 2011, Will Drewry wrote: > Since it seems that there'll be consumers (openssh, vsftpd, kvm/qemu, > chromium, chromium os) and feedback quieted down, what are the next > steps to get this to a pull/no-pull decision points (or at least some > Ack's or Nack's)? I know this patch series crosses a number of > maintainers, and I never know exactly what's next when the feedback > slows down. Are there any outstanding objections to this approach? How do the tracing folk feel about it? -- James Morris -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/