diff options
author | Daniel Borkmann <daniel@iogearbox.net> | 2019-02-23 00:03:44 +0100 |
---|---|---|
committer | Daniel Borkmann <daniel@iogearbox.net> | 2019-02-23 01:22:32 +0100 |
commit | b4b8bb69c104a9345c528692cde5aa520d885360 (patch) | |
tree | abaa1bda1c8c8949676128ff7c6707d750d86223 /net | |
parent | 7d466e5fb13bed595b3a13a8ad054914d56744bf (diff) | |
download | linux-b4b8bb69c104a9345c528692cde5aa520d885360.tar.gz linux-b4b8bb69c104a9345c528692cde5aa520d885360.tar.bz2 linux-b4b8bb69c104a9345c528692cde5aa520d885360.zip |
bpf, doc: add bpf list as secondary entry to maintainers file
We recently created a bpf@vger.kernel.org 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 bpf@vger.kernel.org list that folks can Cc for BPF specific topics.
Acked-by: Alexei Starovoitov <ast@kernel.org>
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions