DAMON development mailing list
 help / color / mirror / Atom feed
From: SJ Park <sj@kernel.org>
To: sashiko-bot@kernel.org
Cc: SJ Park <sj@kernel.org>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"David Hildenbrand" <david@kernel.org>,
	"Jonathan Corbet" <corbet@lwn.net>,
	"Randy Dunlap" <rdunlap@infradead.org>,
	"Shuah Khan" <skhan@linuxfoundation.org>,
	damon@lists.linux.dev, linux-mm@kvack.org
Subject: Re: [RFC PATCH 2/4] Docs/mm/damon/maintainer-profile: use damon.git for patch baselines
Date: Sat, 21 Nov 2026 11:51:42 -0800	[thread overview]
Message-ID: <20261121195144.109526-1-sj@kernel.org> (raw)
In-Reply-To: <sashiko-outbox-227319@kernel.org>

On Sat, 21 Nov 2026 19:42:08 +0000 sashiko-bot@kernel.org wrote:

> Thank you for your contribution! Sashiko AI review found 1 potential
> issue to consider:
> - [Low] Docs/mm/damon: commit message omits MAINTAINERS section name
>   update
> --
> 
> commit 6bab7534a11559ea9b976bf2b9816f3e4a1d90b2
> Author: SJ Park <sj@kernel.org>
> 
> Docs/mm/damon/maintainer-profile: use damon.git for patch baselines
> 
> This commit updates the DAMON maintainer profile documentation to direct
> patches against the damon.git for-next and for-next-fixes trees and updates
> the referenced MAINTAINERS section name.
> 
> > diff --git a/Documentation/mm/damon/maintainer-profile.rst b/Documentation/mm/damon/maintainer-profile.rst
> > index c482690320249..cc6b79c066a64 100644
> > --- a/Documentation/mm/damon/maintainer-profile.rst
> > +++ b/Documentation/mm/damon/maintainer-profile.rst
> > @@ -3,13 +3,20 @@
> >  DAMON Maintainer Entry Profile
> >  ==============================
> >  
> > -The DAMON subsystem covers the files that are listed in 'DAMON' section of
> > -'MAINTAINERS' file.
> > +The DAMON subsystem covers the files that are listed in 'MEMORY MANAGEMENT -
> > +DAMON' section of 'MAINTAINERS' file.
> 
> [Severity: Low]
> This isn't a bug, but the commit message only describes updating the patch
> baseline branches to damon.git and doesn't mention updating the MAINTAINERS
> section name reference to 'MEMORY MANAGEMENT - DAMON'.

Good catch, I will update the commit message in the next spin.

> 
> -- 
> Sashiko AI review · https://sashiko.dev/#/patchset/20261121193331.108587-1-sj@kernel.org?part=2
> 


Thanks,
SJ

  reply	other threads:[~2026-11-21 19:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-21 19:33 [RFC PATCH 0/4] mm/damon: update documents for mm-next onboarding SJ Park
2026-11-21 19:33 ` [RFC PATCH 2/4] Docs/mm/damon/maintainer-profile: use damon.git for patch baselines SJ Park
2026-11-21 19:42   ` sashiko-bot
2026-11-21 19:51     ` SJ Park [this message]
2026-11-21 19:33 ` [RFC PATCH 3/4] Docs/mm/damon/maintainer-profile: drop 'SCM Trees' section SJ Park
2026-11-21 19:33 ` [RFC PATCH 4/4] Docs/mm/damon/maintainer-profile: update key cycle dates for damon.git SJ Park
2026-11-21 19:42 ` [RFC PATCH 0/4] mm/damon: update documents for mm-next onboarding sashiko-bot

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=20261121195144.109526-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=corbet@lwn.net \
    --cc=damon@lists.linux.dev \
    --cc=david@kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rdunlap@infradead.org \
    --cc=sashiko-bot@kernel.org \
    --cc=skhan@linuxfoundation.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