From: Jakub Kicinski <kuba@kernel.org>
To: netdev@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>
Subject: review scoring
Date: Tue, 3 Mar 2026 18:01:22 -0800 [thread overview]
Message-ID: <20260303180122.0929a864@kernel.org> (raw)
Hi!
Alexei just sent an announcement to the BPF list describing
a new system of requiring review participation:
https://lore.kernel.org/all/CAADnVQ+TKKptnNB25V3=bcdybh5G6c2DyW2sYtXvyRaVnPN8MA@mail.gmail.com/
I'm very curious to see how this goes, it definitely feels like
a logical step.
On the netdev side I've been using a patch review queue which
takes into account
- the reviewer score of the author
- the reviewer socre of their employer (using the same logic
I use for the periodic "developer statistics" email),
- quality metrics like "is checkpatch clean"
- whether someone already reviewed the patches on the list
(reviews from the same company do not count)
I've been meaning to send an email to let folks know that I'm doing
this. Most large companies are getting a 2 day delay from this scoring
system. To be clear, I'm not intentionally waiting 2 days before
looking at code (at the cost of my sanity). It's just that with our
patch volume if something gets a 2 day delay there's plenty of patches
that will jump earlier in the queue. And so far advancements in AI
failed to make the days any longer..
the queue: https://netdev.bots.linux.dev/suie.html?delegate=netdev
next reply other threads:[~2026-03-04 2:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 2:01 Jakub Kicinski [this message]
2026-03-05 15:43 ` review scoring Dawid Osuchowski
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=20260303180122.0929a864@kernel.org \
--to=kuba@kernel.org \
--cc=ast@kernel.org \
--cc=netdev@vger.kernel.org \
/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