On Tue, 2024-07-23 at 19:43 -0700, Alexei Starovoitov wrote: > On Tue, Jul 23, 2024 at 7:07 PM Geliang Tang <geliang@xxxxxxxxxx> > wrote: > > > > Hi Alexei, > > > > On Tue, 2024-07-23 at 17:04 -0700, Alexei Starovoitov wrote: > > > I strongly suggest you invest just as much time > > > in reviewing other people's patches as sending yours > > > or they will all be automatically rejected. > > > > Thanks for your reminder. I didn't know that our community has such > > a > > rule. I will try to reduce the number of iterations of my patches > > and > > the number of my emails sent to our community. > > Every patch submission has a cost. A reviewer and/or maintainer > has to process it. You're sending way more than average, > hence depleting the time reviewer/maintainers can spend on other > submissions. This is not ok. > > > I am very willing to review other people's patches, but I am only > > familiar with "BPF [SELFTESTS]" module. If possible, I would like > > to > > add myself (Geliang Tang <geliang@xxxxxxxxxx>) as a reviewer of > > this > > module in MAINTAINERS so that I can receive emails of new patches > > for > > reviewing. Or please add this for me. > > That's not how it works. Anyone can subscribe to bpf@vger and > start reviewing patches. > After some time when developers and maintainers see that > a person commenting on the patches actually adding value > then they will get recognized with R: or M: in the MAINTAINERS file. Got it, thanks for your explanation. -Geliang >
