[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181204114254.0d01bfcb@cakuba.netronome.com>
Date: Tue, 4 Dec 2018 11:42:54 -0800
From: Jakub Kicinski <jakub.kicinski@...ronome.com>
To: Alexei Starovoitov <alexei.starovoitov@...il.com>
Cc: David Miller <davem@...emloft.net>, jiong.wang@...ronome.com,
daniel@...earbox.net, ast@...nel.org, netdev@...r.kernel.org,
oss-drivers@...ronome.com
Subject: Re: [oss-drivers] Re: [RFC bpf-next 1/7] bpf: interpreter support
BPF_ALU | BPF_ARSH
On Tue, 4 Dec 2018 11:29:55 -0800, Alexei Starovoitov wrote:
> Regarding the set... It looks good to me. Pls resubmit without RFC tag
> and probably include mips patch as patch 1, so we can apply the whole
> thing to bpf-next. git will take care of same patch being in two trees.
Doesn't it only take care if the commit id matches? I.e. if you were
to pull the MIPS tree?
Powered by blists - more mailing lists