Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933524AbaFCUgb (ORCPT ); Tue, 3 Jun 2014 16:36:31 -0400 Received: from mx1.redhat.com ([209.132.183.28]:22483 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753324AbaFCUga (ORCPT ); Tue, 3 Jun 2014 16:36:30 -0400 Message-ID: <538E319B.3000606@redhat.com> Date: Tue, 03 Jun 2014 22:35:39 +0200 From: Daniel Borkmann User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Alexei Starovoitov CC: "David S. Miller" , Ingo Molnar , Steven Rostedt , Chema Gonzalez , Eric Dumazet , Peter Zijlstra , Arnaldo Carvalho de Melo , Jiri Olsa , Thomas Gleixner , "H. Peter Anvin" , Andrew Morton , Kees Cook , Network Development , LKML Subject: Re: [PATCH v2 net-next 0/2] split BPF out of core networking References: <1401692506-7796-1-git-send-email-ast@plumgrid.com> <538C3C94.3080206@redhat.com> <538CAEA6.4060307@redhat.com> <538D8DAA.7090105@redhat.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 06/03/2014 05:44 PM, Alexei Starovoitov wrote: ... > All of your points are valid. They are right questions to ask. I just > don't see why you're still arguing about first step of filter.c split, > whereas your concerns are about steps 2, 3, 4. Fair enough, lets keep them in mind though for future work. Btw, are other files planned for kernel/bpf/ or should it instead just simply be kernel/bpf.c? -- 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/