From: Jakub Kicinski <kuba@kernel.org>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Daniel Borkmann <daniel@iogearbox.net>, bpf <bpf@vger.kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>, Yonghong Song <yhs@fb.com>,
Mykola Lysenko <mykolal@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
Jiri Olsa <jolsa@kernel.org>, KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>,
Quentin Monnet <quentin@isovalent.com>
Subject: Re: [PATCH bpf] bpf, docs: Better scale maintenance of BPF subsystem
Date: Mon, 27 Jun 2022 13:30:27 -0700 [thread overview]
Message-ID: <20220627133027.1e141f11@kernel.org> (raw)
In-Reply-To: <CAADnVQLOS4kvmcp+aaX6gtDUCUfoL906K+Y4KUZOsYBDso_xMw@mail.gmail.com>
On Mon, 27 Jun 2022 12:57:21 -0700 Alexei Starovoitov wrote:
> And that's a good thing.
My concern is that folks will rebel against populating the CC list if
they never receive feedback from the CCed. I often have to go and
manually trim the CC list because I don't think Jiri, KP, Yonghong etc.
care about my random TLS patch, or removal of a driver which happens
to contain the letters "bpf". I was hoping the delegation you're
performing could help with the large Cc list. Would you perhaps
consider moving the K/N regexes to the "Core" entry? It'd lower
the pain of false positives.
> 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.
Yeah, Exhibit A - vger is lagging right now...
I guess the "real fix" is on the vger, trying to massage MAINTAINERS
now is not a great use of time..
next prev parent reply other threads:[~2022-06-27 20:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 18:22 [PATCH bpf] bpf, docs: Better scale maintenance of BPF subsystem Daniel Borkmann
2022-06-27 19:26 ` Jakub Kicinski
2022-06-27 19:57 ` Alexei Starovoitov
2022-06-27 20:30 ` Jakub Kicinski [this message]
2022-06-27 20:38 ` Alexei Starovoitov
2022-06-28 8:59 ` Daniel Borkmann
2022-06-28 16:46 ` Alexei Starovoitov
2022-06-28 16:56 ` Daniel Borkmann
2022-06-28 16:57 ` Jakub Kicinski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220627133027.1e141f11@kernel.org \
--to=kuba@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=quentin@isovalent.com \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=yhs@fb.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).