All of lore.kernel.org
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: Shakeel Butt <shakeel.butt@linux.dev>
Cc: SeongJae Park <sj@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org
Subject: Re: mm.git review status (mm-stable)
Date: Tue,  3 Feb 2026 22:50:28 -0800	[thread overview]
Message-ID: <20260204065029.16046-1-sj@kernel.org> (raw)
In-Reply-To: <aYIdEKHZ9mss9ZJb@linux.dev>

On Tue, 3 Feb 2026 08:18:18 -0800 Shakeel Butt <shakeel.butt@linux.dev> wrote:

> On Mon, Feb 02, 2026 at 06:45:52PM -0800, Andrew Morton wrote:
> > 
> > I wrote a thing, thought it might be of some interest.
> > 
> > 
> > mm.git review status for linus..mm-stable
> > 
> > Everything:
> > 
> > Total patches:       320
> > Reviews/patch:       1.40
> > Reviewed rate:       74%

Thank you for sharing this, Andrew :)  This high level view is helpful.

> > 
> > Excluding DAMON:
> > 
> > Total patches:       259
> > Reviews/patch:       1.65
> > Reviewed rate:       84%

And the above part made me wonder if there could be people who want to get the
view for only DAMON patches.  I was actually wondering that recently, and
therefore was writing a tool [1] that can provide that kind of information,
occasionally in the last weekend.  The tool is still in a early stage, so it
would be buggy and may be changed a lot in near future.  Nonetheless, it can
provide the review status in multiple categories [2] including if it is not
reviewed but written by a maintainer, and for specific subsystems.  So if you
want to know more detailed review status of patches for DAMON or other
subsystems in mm tree, you could use it.  E.g.,

    $ ../lazybox/linux_hack/mm_tree_summary.py --subsystem "DAMON" --review_score_to_print_commits 11
    baseline: v6.19-rc6-36-g6c790212c588f

    # DAMON
    mm-hotfixes-stable: 0 commits
    mm-hotfixes-unstable: 0 commits
    mm-stable: 62 commits
      - review score 3: 12 commits
      - review score 8: 42 commits
      - review score 9: 7 commits
      - review score 11: 1 commits
        - 95296536eb19 ("memcg: rename mem_cgroup_ino() to mem_cgroup_id()")
    mm-unstable: 1 commits
      - review score 3: 1 commits
    mm-new: 1 commits
      - review score 3: 1 commits
    mm-nonmm-stable: 0 commits
    mm-nonmm-unstable: 0 commits

> > 
> > Excluding DAMON and zram:
> > 
> > Total patches:       245
> > Reviews/patch:       1.74
> > Reviewed rate:       88%
> > 
> 
> Thanks Andrew for sharing this. It seems like DAMON and zram maintainers
> need to convince more folks to be reviewers for their sub-system :P

I just hope my code makes more reviewers than my words and chocolate cakes ;)

[1] https://github.com/sjp38/lazybox/blob/master/linux_hack/mm_tree_summary.py
[2] https://github.com/sjp38/lazybox/blob/master/linux_hack/mm_tree_summary.py#L64


Thanks,
SJ

[...]


      reply	other threads:[~2026-02-04  6:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-03  2:45 mm.git review status (mm-stable) Andrew Morton
2026-02-03 16:18 ` Shakeel Butt
2026-02-04  6:50   ` SeongJae Park [this message]

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=20260204065029.16046-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=shakeel.butt@linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.