From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Jiong Wang <jiong.wang@netronome.com>
Cc: ast@kernel.org, daniel@iogearbox.net,
jakub.kicinski@netronome.com, netdev@vger.kernel.org,
oss-drivers@netronome.com
Subject: Re: [PATCH bpf-next 0/2] nfp: bpf: shifts support cleanups
Date: Fri, 1 Feb 2019 21:39:10 -0800 [thread overview]
Message-ID: <20190202053908.6ubjfcm4uvxcfutg@ast-mbp> (raw)
In-Reply-To: <1549060769-20920-1-git-send-email-jiong.wang@netronome.com>
On Fri, Feb 01, 2019 at 10:39:27PM +0000, Jiong Wang wrote:
> NFP JIT back-end is missing several ALU32 logic shifts support.
>
> Also, shifts with shift amount be zero are not handled properly.
>
> This set cleans up these issues.
Applied, Thanks
prev parent reply other threads:[~2019-02-02 5:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 22:39 [PATCH bpf-next 0/2] nfp: bpf: shifts support cleanups Jiong Wang
2019-02-01 22:39 ` [PATCH bpf-next 1/2] nfp: bpf: correct the behavior for shifts by zero Jiong Wang
2019-02-01 22:39 ` [PATCH bpf-next 2/2] nfp: bpf: complete ALU32 logic shift supports Jiong Wang
2019-02-02 5:39 ` Alexei Starovoitov [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=20190202053908.6ubjfcm4uvxcfutg@ast-mbp \
--to=alexei.starovoitov@gmail.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=jakub.kicinski@netronome.com \
--cc=jiong.wang@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