From: "Theodore Tso" <tytso@mit.edu>
To: Bradley Morgan <include@grrlz.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, pmladek@suse.com
Subject: Re: [RFC] kernel/ review rules
Date: Fri, 21 Aug 2026 08:13:08 -0400 [thread overview]
Message-ID: <aog_PS002Rwcm97n@mit.edu> (raw)
In-Reply-To: <12408214-5B8C-4103-A8D1-FC15D4586F8D@grrlz.net>
On Fri, Aug 21, 2026 at 08:30:02AM -0500, Bradley Morgan wrote:
> >Acked-by: "cool changelog!"
As a maintainer, I completely ignore an Acked-by unless it comes from
another Maintainer, in which case it means that the other Maintainer
is OK with that commit which might affect their subsystem (either
directly because it modifies code in their subsystem or indirectly
because it changes functions that their subsystem depends upon).
As a result I will likely drop an Acked-by and not include it in the
git commit descritpion if it comes from a non-Maintainer.
> >Reviewed-by: + nothing "cool changelog and I scrolled through it"
> >Reviewed-by: + commentary: "I reviewed it!"
If there is a reviewed-by, and other problems are discovered by other
reviewers, the reputation of the person who submitted the Reviewed-by
will go down, and with enough bogus reviewed-by, I will start ignoring
that reviewer and drop their Reviewed-by from the git commit
description.
And if there is Reviewed-by commentary which is actively wrong, I may
start sending patch submitters form letters informing them that they
should feel free to ignore reviews from Reviewer XXXXX since the
reviews may be unreliable.
So I wouldn't focus on review numbers, but review *quality*.
Cheers,
- Ted
next prev parent reply other threads:[~2026-08-21 12:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 0:20 Bradley Morgan
2026-08-21 1:00 ` Andrew Morton
2026-08-21 7:30 ` Bradley Morgan
2026-08-21 12:13 ` Theodore Tso [this message]
2026-08-21 16:39 ` Bradley Morgan
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=aog_PS002Rwcm97n@mit.edu \
--to=tytso@mit.edu \
--cc=akpm@linux-foundation.org \
--cc=include@grrlz.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.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
all inboxes | Powered by JetHome®