On Tue, Nov 27, 2018 at 01:21:00AM +0100, Daniel Borkmann wrote: > Make the high-level BPF JIT entry a general 'catch-all' and add > architecture specific entries to make it more clear who actively > maintains which BPF JIT compiler. The list (L) address implies > that this eventually lands in the bpf patchwork bucket. Goal is > that this set of responsible developers listed here is always up > to date and a point of contact for helping out in e.g. feature > development, fixes, review or testing patches in order to help > long-term in ensuring quality of the BPF JITs and therefore BPF > core under a given architecture. Every new JIT in future /must/ > have an entry here as well. > > Signed-off-by: Daniel Borkmann <dan...@iogearbox.net> > Acked-by: Alexei Starovoitov <a...@kernel.org> > Acked-by: Naveen N. Rao <naveen.n....@linux.vnet.ibm.com> > Acked-by: Sandipan Das <sandi...@linux.ibm.com> > Acked-by: Martin Schwidefsky <schwidef...@de.ibm.com> > Acked-by: Heiko Carstens <heiko.carst...@de.ibm.com> > Acked-by: David S. Miller <da...@davemloft.net> > Acked-by: Zi Shen Lim <zlim....@gmail.com> > Acked-by: Paul Burton <paul.bur...@mips.com> > Acked-by: Jakub Kicinski <jakub.kicin...@netronome.com> > Acked-by: Wang YanQing <udkni...@gmail.com>
Applied to bpf tree.
