linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Denis Kirjanov <kda@linux-powerpc.org>
Cc: netdev@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH net-next 1/6] ppc: Kconfig: Enable BPF JIT on ppc32
Date: Sun, 15 Feb 2015 10:15:54 -0800	[thread overview]
Message-ID: <1424024154.2685.1.camel@perches.com> (raw)
In-Reply-To: <1424023605-2416-2-git-send-email-kda@linux-powerpc.org>

On Sun, 2015-02-15 at 21:06 +0300, Denis Kirjanov wrote:
[]
> diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig
[]
> @@ -126,7 +126,7 @@ config PPC
>  	select IRQ_FORCED_THREADING
>  	select HAVE_RCU_TABLE_FREE if SMP
>  	select HAVE_SYSCALL_TRACEPOINTS
> -	select HAVE_BPF_JIT if PPC64
> +	select HAVE_BPF_JIT

trivia:

Should this be the last patch of the series?

  reply	other threads:[~2015-02-15 18:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-15 18:06 [PATCH net-next 0/6] bpf: Enable BPF JIT on ppc32 Denis Kirjanov
2015-02-15 18:06 ` [PATCH net-next 1/6] ppc: Kconfig: " Denis Kirjanov
2015-02-15 18:15   ` Joe Perches [this message]
2015-02-15 19:07     ` David Miller
2015-02-15 19:16       ` Denis Kirjanov
2015-02-15 18:06 ` [PATCH net-next 2/6] ppc: bpf: add required compatibility macros for jit Denis Kirjanov
2015-02-15 18:06 ` [PATCH net-next 3/6] ppc: bpf: add reqired opcodes for ppc32 Denis Kirjanov
2015-02-15 18:06 ` [PATCH net-next 4/6] ppc: bpf: update jit to use compatibility macros Denis Kirjanov
2015-02-15 18:06 ` [PATCH net-next 5/6] ppc: bpf: rename bpf_jit_64.S to bpf_jit_asm.S Denis Kirjanov
2015-02-15 18:06 ` [PATCH net-next 6/6] ppc: bpf: Add SKF_AD_CPU for ppc32 Denis Kirjanov
2015-02-15 20:09 ` [PATCH net-next 0/6] bpf: Enable BPF JIT on ppc32 Daniel Borkmann
2015-02-16  7:13   ` Denis Kirjanov
2015-02-16 16:01     ` Daniel Borkmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1424024154.2685.1.camel@perches.com \
    --to=joe@perches.com \
    --cc=kda@linux-powerpc.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).