linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: kda@linux-powerpc.org
Cc: netdev@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: bpf: Enable BPF JIT on ppc32
Date: Fri, 20 Feb 2015 15:20:21 -0500 (EST)	[thread overview]
Message-ID: <20150220.152021.2226608147725066444.davem@davemloft.net> (raw)
In-Reply-To: <1424156683-2682-1-git-send-email-kda@linux-powerpc.org>

aFrom: Denis Kirjanov <kda@linux-powerpc.org>
Date: Tue, 17 Feb 2015 10:04:37 +0300

> This patch series enables BPF JIT on ppc32. There are relatevily
> few chnages in the code to make it work.
> 
> All test_bpf tests passed both on 7447a and P2041-based machines.
> 
> Changelog:
> v1 - > v2: Reordered Kconfig patch in the series

Series applied to net-next, thanks.

      parent reply	other threads:[~2015-02-20 20:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-17  7:04 bpf: Enable BPF JIT on ppc32 Denis Kirjanov
2015-02-17  7:04 ` [PATCH net-next v2 1/6] ppc: bpf: add required compatibility macros for jit Denis Kirjanov
2015-02-17  7:04 ` [PATCH net-next v2 2/6] ppc: bpf: add reqired opcodes for ppc32 Denis Kirjanov
2015-02-17  7:04 ` [PATCH net-next v2 3/6] ppc: bpf: update jit to use compatibility macros Denis Kirjanov
2015-02-17  7:04 ` [PATCH net-next v2 4/6] ppc: bpf: rename bpf_jit_64.S to bpf_jit_asm.S Denis Kirjanov
2015-02-17  7:04 ` [PATCH net-next v2 5/6] ppc: bpf: Add SKF_AD_CPU for ppc32 Denis Kirjanov
2015-02-17  7:04 ` [PATCH net-next v2 6/6] ppc: Kconfig: Enable BPF JIT on ppc32 Denis Kirjanov
2015-02-19 20:56 ` bpf: " David Miller
2015-02-19 21:07   ` Denis Kirjanov
2015-02-19 21:26     ` Michael Ellerman
2015-02-19 21:35       ` Denis Kirjanov
2015-02-20 20:20 ` David Miller [this message]

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=20150220.152021.2226608147725066444.davem@davemloft.net \
    --to=davem@davemloft.net \
    --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).