From: David Miller <davem@davemloft.net>
To: jakub.kicinski@netronome.com
Cc: netdev@vger.kernel.org, oss-drivers@netronome.com
Subject: Re: [PATCH net-next 0/2] nfp: bpf: rename ALU_OP_NEG and support BPF_NEG
Date: Thu, 02 Nov 2017 16:47:48 +0900 (KST) [thread overview]
Message-ID: <20171102.164748.1852340900831595296.davem@davemloft.net> (raw)
In-Reply-To: <20171101173825.7008-1-jakub.kicinski@netronome.com>
From: Jakub Kicinski <jakub.kicinski@netronome.com>
Date: Wed, 1 Nov 2017 10:38:23 -0700
> Jiong says:
>
> Compilers are starting to use BPF_NEG, for example LLVM. However, NFP
> does not support JITing it. This patch set adds this. Unit test is added
> as well.
>
> Meanwhile, the current NFP_ALU_NEG is actually doing bitwise NOT (one's
> complement) operation, so the name is misleading. This patch set corrects
> this.
Series applied, thanks.
prev parent reply other threads:[~2017-11-02 7:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 17:38 [PATCH net-next 0/2] nfp: bpf: rename ALU_OP_NEG and support BPF_NEG Jakub Kicinski
2017-11-01 17:38 ` [PATCH net-next 1/2] nfp: bpf: rename ALU_OP_NEG to ALU_OP_NOT Jakub Kicinski
2017-11-01 17:38 ` [PATCH net-next 2/2] nfp: bpf: support [BPF_ALU | BPF_ALU64] | BPF_NEG Jakub Kicinski
2017-11-02 7:47 ` 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=20171102.164748.1852340900831595296.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jakub.kicinski@netronome.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.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).