From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Borkmann Subject: Re: [PATCH v2 net-next 0/2] split BPF out of core networking Date: Tue, 03 Jun 2014 22:35:39 +0200 Message-ID: <538E319B.3000606@redhat.com> References: <1401692506-7796-1-git-send-email-ast@plumgrid.com> <538C3C94.3080206@redhat.com> <538CAEA6.4060307@redhat.com> <538D8DAA.7090105@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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 To: Alexei Starovoitov Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.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?