aboutsummaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/check-perf-trace.py
diff options
context:
space:
mode:
authorDaniel Borkmann <[email protected]>2019-02-22 23:03:44 +0000
committerDaniel Borkmann <[email protected]>2019-02-23 00:22:32 +0000
commitb4b8bb69c104a9345c528692cde5aa520d885360 (patch)
treeabaa1bda1c8c8949676128ff7c6707d750d86223 /tools/perf/scripts/python/check-perf-trace.py
parentMerge branch 'bpf-nfp-codegen-fixes' (diff)
downloadkernel-b4b8bb69c104a9345c528692cde5aa520d885360.tar.gz
kernel-b4b8bb69c104a9345c528692cde5aa520d885360.zip
bpf, doc: add bpf list as secondary entry to maintainers file
We recently created a [email protected] list (https://lore.kernel.org/bpf/) for BPF related discussions, originally in context of BPF track at LSF/MM for topic discussions. It's *optional* but *desirable* to keep it in Cc for BPF related kernel/loader/llvm/tooling threads, meaning also infrastructure like llvm that sits on top of kernel but is crucial to BPF. In any case, netdev with it's bpf delegate is *as-is* today primary list for patches, so nothing changes in the workflow. Main purpose is to have some more awareness for the [email protected] list that folks can Cc for BPF specific topics. Acked-by: Alexei Starovoitov <[email protected]> Signed-off-by: Daniel Borkmann <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/check-perf-trace.py')
0 files changed, 0 insertions, 0 deletions