On Mon, Jun 27, 2022 at 12:26 PM Jakub Kicinski <kuba@xxxxxxxxxx> wrote: > > On Mon, 27 Jun 2022 20:22:55 +0200 Daniel Borkmann wrote: > > -BPF (Safe dynamic programs and tools) > > +BPF [GENERAL] (Safe Dynamic Programs and Tools) > > M: Alexei Starovoitov <ast@xxxxxxxxxx> > > M: Daniel Borkmann <daniel@xxxxxxxxxxxxx> > > M: Andrii Nakryiko <andrii@xxxxxxxxxx> > > -R: Martin KaFai Lau <kafai@xxxxxx> > > -R: Song Liu <songliubraving@xxxxxx> > > +R: Martin KaFai Lau <martin.lau@xxxxxxxxx> > > +R: Song Liu <song@xxxxxxxxxx> > > R: Yonghong Song <yhs@xxxxxx> > > R: John Fastabend <john.fastabend@xxxxxxxxx> > > R: KP Singh <kpsingh@xxxxxxxxxx> > > -L: netdev@xxxxxxxxxxxxxxx > > +R: Stanislav Fomichev <sdf@xxxxxxxxxx> > > +R: Hao Luo <haoluo@xxxxxxxxxx> > > +R: Jiri Olsa <jolsa@xxxxxxxxxx> > > L: bpf@xxxxxxxxxxxxxxx > > S: Supported > > W: https://bpf.io/ > > Can we pause and think a bit about the purpose for this entry? I've been > trying to make people obey get_maintainer.pl but having to CC 11 people > is a asking a lot - especially that this entry regexp-keys on BPF (K: > bpf N: bpf). So any patch that as much as uses the letters "bpf" gets > an enormous CC list. And that's a good thing. vger continues to cause trouble and it doesn't sound that the fix is coming. So having everyone directly cc-ed is the only option we have.
