netdev - Re: [oss-drivers] Re: [RFC bpf-next 1/7] bpf: interpreter support BPF_ALU

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20181204200028.psbdmfoiuv3lhrbk@ast-mbp.dhcp.thefacebook.com>
Date:   Tue, 4 Dec 2018 12:00:30 -0800
From:   Alexei Starovoitov <alexei.starovoitov@...il.com>
To:     Jakub Kicinski <jakub.kicinski@...ronome.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, Dec 04, 2018 at 11:42:54AM -0800, Jakub Kicinski wrote:
> 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?

I think we've tried that before. As long as all text of the patch
is the same (including commit log), git will not complain.
fingers crossed :)