[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190126213946.kfmcidduv2q3mf3y@ast-mbp>
Date: Sat, 26 Jan 2019 13:39:48 -0800
From: Alexei Starovoitov <alexei.starovoitov@...il.com>
To: Jiong Wang <jiong.wang@...ronome.com>
Cc: ast@...nel.org, daniel@...earbox.net, netdev@...r.kernel.org,
oss-drivers@...ronome.com,
"David S . Miller" <davem@...emloft.net>,
Paul Burton <paul.burton@...s.com>,
Wang YanQing <udknight@...il.com>,
Zi Shen Lim <zlim.lnx@...il.com>,
Shubham Bansal <illusionist.neo@...il.com>,
"Naveen N . Rao" <naveen.n.rao@...ux.ibm.com>,
Sandipan Das <sandipan@...ux.ibm.com>,
Martin Schwidefsky <schwidefsky@...ibm.com>,
Heiko Carstens <heiko.carstens@...ibm.com>
Subject: Re: [PATCH bpf-next v4 00/16] bpf: propose new jmp32 instructions
On Sat, Jan 26, 2019 at 12:25:58PM -0500, Jiong Wang wrote:
> v3 -> v4:
> - Fixed rebase issue. JMP32 checks were missing in two new functions:
> + kernel/bpf/verifier.c:insn_is_cond_jump
> + drivers/net/ethernet/netronome/nfp/bpf/main.h:is_mbpf_cond_jump
> (Daniel)
> - Further rebased on top of latest llvm-readelf change.
Applied to bpf-next.
Thanks!
Powered by blists - more mailing lists