From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754830AbbGUDfJ (ORCPT ); Mon, 20 Jul 2015 23:35:09 -0400 Received: from shards.monkeyblade.net ([149.20.54.216]:54415 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752077AbbGUDfG (ORCPT ); Mon, 20 Jul 2015 23:35:06 -0400 Date: Mon, 20 Jul 2015 20:35:05 -0700 (PDT) Message-Id: <20150720.203505.673166237258951387.davem@davemloft.net> To: nschichan@freebox.fr Cc: dborkman@redhat.com, mgherzan@gmail.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, linux@arm.linux.org.uk, ast@plumgrid.com Subject: Re: [PATCH 0/6] BPF JIT fixes and features for ARM From: David Miller In-Reply-To: <1437065195-10887-1-git-send-email-nschichan@freebox.fr> References: <1437065195-10887-1-git-send-email-nschichan@freebox.fr> X-Mailer: Mew version 6.6 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Mon, 20 Jul 2015 20:35:06 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Nicolas Schichan Date: Thu, 16 Jul 2015 18:46:29 +0200 > This serie fixes issues with the ARM BPF JIT and adds support for more > instructions to the ARM BPF JIT. > > The first three patches are fixing bugs in the ARM JIT and should > probably find their way to a stable kernel. > > The last three patches add support to the ARM JIT for more BPF > instructions, namely skb netdevice type retrieval, skb payload offset > retrieval, and skb packet type retrieval. > > With the first three patches, all 60 test_bpf tests in Linux 4.1 release > are now passing OK (was 54 out of 60 before). > > The last three patches allow 35 tests to use the JIT instead of 29 > before. > > Like previous ARM JIT patches this should go via the net tree. You've submitted this in a manner which is very mixed up and difficult for me to handle. For the bug fixes, create a separate series that targets the 'net' tree. Next, create another series with the new features that target 'net-next'. Carefully and clearly indicate that the series depends upon the bug fix one and I'll sort it out. Thanks.