From: Daniel Borkmann <daniel@iogearbox.net>
To: Sandipan Das <sandipan@linux.ibm.com>
Cc: naveen.n.rao@linux.ibm.com, linuxppc-dev@lists.ozlabs.org,
ast@kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH bpf] bpf: powerpc64: optimize JIT passes for bpf function calls
Date: Mon, 3 Dec 2018 23:53:54 +0100 [thread overview]
Message-ID: <a80f6fd5-181b-01a5-a7a4-2e8f1911ffac@iogearbox.net> (raw)
In-Reply-To: <03a23ff9-1337-74dc-74e5-c5132909f8be@linux.ibm.com>
On 12/03/2018 02:26 PM, Sandipan Das wrote:
> Hi Daniel,
>
> On 03/12/18 6:18 PM, Daniel Borkmann wrote:
>>
>> Thanks for the patch, just to clarify, it's targeted at bpf-next and
>> not bpf, correct?
>
> This patch is targeted at the bpf tree.
Ok, thanks for clarifying, applied to bpf!
prev parent reply other threads:[~2018-12-03 23:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 12:21 [PATCH bpf] bpf: powerpc64: optimize JIT passes for bpf function calls Sandipan Das
2018-12-03 12:48 ` Daniel Borkmann
2018-12-03 13:26 ` Sandipan Das
2018-12-03 22:53 ` Daniel Borkmann [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=a80f6fd5-181b-01a5-a7a4-2e8f1911ffac@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=naveen.n.rao@linux.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=sandipan@linux.ibm.com \
/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).