Documentation/mm/damon/maintainer-profile.rst | 21 +++++++++++++++++++ 1 file changed, 21 insertions(+)
DAMON is opted-in for DAMON patches scanning [1] and email delivery [2].
Clarify how that could be used on DAMON maintainer profile.
[1] https://github.com/sashiko-dev/sashiko/commit/ad9f4a98f958
[2] https://github.com/sashiko-dev/sashiko/commit/b554c7b6e733
Signed-off-by: SeongJae Park <sj@kernel.org>
---
Documentation/mm/damon/maintainer-profile.rst | 21 +++++++++++++++++++
1 file changed, 21 insertions(+)
diff --git a/Documentation/mm/damon/maintainer-profile.rst b/Documentation/mm/damon/maintainer-profile.rst
index bcb9798a27a86..5c23b1281c50c 100644
--- a/Documentation/mm/damon/maintainer-profile.rst
+++ b/Documentation/mm/damon/maintainer-profile.rst
@@ -100,3 +100,24 @@ There is also a public Google `calendar
<https://calendar.google.com/calendar/u/0?cid=ZDIwOTA4YTMxNjc2MDQ3NTIyMmUzYTM5ZmQyM2U4NDA0ZGIwZjBiYmJlZGQxNDM0MmY4ZTRjOTE0NjdhZDRiY0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t>`_
that has the events. Anyone can subscribe to it. DAMON maintainer will also
provide periodic reminders to the mailing list (damon@lists.linux.dev).
+
+AI Review
+---------
+
+For patches that are publicly posted to DAMON mailing list
+(damon@lists.linux.dev), AI reviews of the patches will be available at
+sashiko.dev. The reviews could also be sent as mails to the author of the
+patch.
+
+Patch authors are encouraged to check the AI reviews and share their opinions.
+The sharing could be done as a reply to the mail thread. Consider reducing the
+recipients list for such sharing, since some people are not really interested
+in AI reviews. As a rule of thumb, drop individuals except DAMON maintainer
+and stable@vger.kernel.org from the recipients list.
+
+`hkml` also provides a `feature
+<https://github.com/sjp38/hackermail/blob/master/USAGE.md#forwarding-sashikodev-statuscomments-to-mailing-list>`_
+for such sharing. Please feel free to use the feature.
+
+It is only a non-mandastory recommendation. DAMON maintainer could also ask
+any question about the AI reviews, though.
base-commit: aeaae01df7d17b5742e22b65b06f666ddea76816
--
2.47.3
# sashiko review suggestions # # 1. Consider reducing recipients. Maybe the author, # maintainers, reviewers, and mailing list of the # direct subsystem and parent susystem mailing lists # could be a starting point. # 2. Add short summary of your opinion at the beginning. # For example: # # TL;DR: sashiko found an issue. I will respin. # TL;DR: sashiko found no issue on this patch. # # Please DON'T FORGET removing this comment block before # sending this! Forwarding full sashiko review in a reply format with my inline comments below, for sharing details of my view and doing followup discussions via mails if needed. > # review url: https://sashiko.dev/#/patchset/20260411174906.79491-1-sj@kernel.org > # start of sashiko.dev inline review > commit eaf13e650de39668ddb68467088d425fa3e8be04 > Author: SeongJae Park <sj@kernel.org> > > Docs/mm/damon/maintainer-profile: add AI review usage guideline > > This commit clarifies how the DAMON maintainer profile uses sashiko.dev for > AI patch scanning and email delivery. It adds a new AI Review section > explaining how patch authors can check reviews and share their opinions. > > > diff --git a/Documentation/mm/damon/maintainer-profile.rst b/Documentation/mm/damon/maintainer-profile.rst > > index bcb9798a27a86..5c23b1281c50c 100644 > > --- a/Documentation/mm/damon/maintainer-profile.rst > > +++ b/Documentation/mm/damon/maintainer-profile.rst > > @@ -100,3 +100,24 @@ There is also a public Google `calendar > > <https://calendar.google.com/calendar/u/0?cid=ZDIwOTA4YTMxNjc2MDQ3NTIyMmUzYTM5ZmQyM2U4NDA0ZGIwZjBiYmJlZGQxNDM0MmY4ZTRjOTE0NjdhZDRiY0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t>`_ > > that has the events. Anyone can subscribe to it. DAMON maintainer will also > > provide periodic reminders to the mailing list (damon@lists.linux.dev). > > + > > +AI Review > > +--------- > > + > > +For patches that are publicly posted to DAMON mailing list > > +(damon@lists.linux.dev), AI reviews of the patches will be available at > > +sashiko.dev. The reviews could also be sent as mails to the author of the > > +patch. > > + > > +Patch authors are encouraged to check the AI reviews and share their opinions. > > +The sharing could be done as a reply to the mail thread. Consider reducing the > > +recipients list for such sharing, since some people are not really interested > > +in AI reviews. As a rule of thumb, drop individuals except DAMON maintainer > > +and stable@vger.kernel.org from the recipients list. > > Is stable@vger.kernel.org the correct mailing list to keep here? > > The stable mailing list is exclusively for stable kernel backports. Sending > ongoing patch AI review discussions to that list could result in spamming it. > Should this perhaps be damon@lists.linux.dev instead? I mean, drop individuals except DAMON maintainer, and also drop stable@. I will wordsmith like below: ''' --- a/Documentation/mm/damon/maintainer-profile.rst +++ b/Documentation/mm/damon/maintainer-profile.rst @@ -112,8 +112,8 @@ patch. Patch authors are encouraged to check the AI reviews and share their opinions. The sharing could be done as a reply to the mail thread. Consider reducing the recipients list for such sharing, since some people are not really interested -in AI reviews. As a rule of thumb, drop individuals except DAMON maintainer -and stable@vger.kernel.org from the recipients list. +in AI reviews. As a rule of thumb, drop stable@vger.kernel.org and individuals +except DAMON maintainer. `hkml` also provides a `feature <https://github.com/sjp38/hackermail/blob/master/USAGE.md#forwarding-sashikodev-statuscomments-to-mailing-list>`_ ''' > > > + > > +`hkml` also provides a `feature > > +<https://github.com/sjp38/hackermail/blob/master/USAGE.md#forwarding-sashikodev-statuscomments-to-mailing-list>`_ > > +for such sharing. Please feel free to use the feature. > > + > > +It is only a non-mandastory recommendation. DAMON maintainer could also ask > > This isn't a bug, but there's a typo (non-mandastory) here. It should be > non-mandatory. Good eye. Randy also found [1] this and I already promised to fix. Sashiko is better than google doc [2]! > > > +any question about the AI reviews, though. > > > # end of sashiko.dev inline review > # review url: https://sashiko.dev/#/patchset/20260411174906.79491-1-sj@kernel.org [1] https://lore.kernel.org/20aa1471-5257-4913-ae46-7b40ca0aa128@infradead.org [2] https://lore.kernel.org/20260411183029.81030-1-sj@kernel.org Thanks, SJ # hkml [1] generated a draft of this mail. You can regenerate # this using below command: # # hkml patch sashiko_dev --for_forwarding \ # 20260411174906.79491-1-sj@kernel.org # # [1] https://github.com/sjp38/hackermail
On Sat, 11 Apr 2026 11:48:01 -0700 SeongJae Park <sj@kernel.org> wrote: > # sashiko review suggestions > # > # 1. Consider reducing recipients. Maybe the author, > # maintainers, reviewers, and mailing list of the > # direct subsystem and parent susystem mailing lists > # could be a starting point. > # 2. Add short summary of your opinion at the beginning. > # For example: > # > # TL;DR: sashiko found an issue. I will respin. > # TL;DR: sashiko found no issue on this patch. > # > # Please DON'T FORGET removing this comment block before > # sending this! I forgot following my self guideline above. Sorry for the noise. TL; DR: sashiko found an issue that better to be fixed. I will respin. Thanks, SJ [...]
On 4/11/26 10:49 AM, SeongJae Park wrote:
> DAMON is opted-in for DAMON patches scanning [1] and email delivery [2].
> Clarify how that could be used on DAMON maintainer profile.
>
> [1] https://github.com/sashiko-dev/sashiko/commit/ad9f4a98f958
> [2] https://github.com/sashiko-dev/sashiko/commit/b554c7b6e733
>
> Signed-off-by: SeongJae Park <sj@kernel.org>
> ---
> Documentation/mm/damon/maintainer-profile.rst | 21 +++++++++++++++++++
> 1 file changed, 21 insertions(+)
>
> diff --git a/Documentation/mm/damon/maintainer-profile.rst b/Documentation/mm/damon/maintainer-profile.rst
> index bcb9798a27a86..5c23b1281c50c 100644
> --- a/Documentation/mm/damon/maintainer-profile.rst
> +++ b/Documentation/mm/damon/maintainer-profile.rst
> @@ -100,3 +100,24 @@ There is also a public Google `calendar
> <https://calendar.google.com/calendar/u/0?cid=ZDIwOTA4YTMxNjc2MDQ3NTIyMmUzYTM5ZmQyM2U4NDA0ZGIwZjBiYmJlZGQxNDM0MmY4ZTRjOTE0NjdhZDRiY0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t>`_
> that has the events. Anyone can subscribe to it. DAMON maintainer will also
> provide periodic reminders to the mailing list (damon@lists.linux.dev).
> +
> +AI Review
> +---------
> +
> +For patches that are publicly posted to DAMON mailing list
> +(damon@lists.linux.dev), AI reviews of the patches will be available at
> +sashiko.dev. The reviews could also be sent as mails to the author of the
> +patch.
> +
> +Patch authors are encouraged to check the AI reviews and share their opinions.
> +The sharing could be done as a reply to the mail thread. Consider reducing the
> +recipients list for such sharing, since some people are not really interested
> +in AI reviews. As a rule of thumb, drop individuals except DAMON maintainer
> +and stable@vger.kernel.org from the recipients list.
> +
> +`hkml` also provides a `feature
> +<https://github.com/sjp38/hackermail/blob/master/USAGE.md#forwarding-sashikodev-statuscomments-to-mailing-list>`_
> +for such sharing. Please feel free to use the feature.
> +
> +It is only a non-mandastory recommendation. DAMON maintainer could also ask
non-mandatory
or maybe
This is an optional recommendation.
> +any question about the AI reviews, though.
>
> base-commit: aeaae01df7d17b5742e22b65b06f666ddea76816
--
~Randy
On Sat, 11 Apr 2026 11:27:14 -0700 Randy Dunlap <rdunlap@infradead.org> wrote: > > > On 4/11/26 10:49 AM, SeongJae Park wrote: > > DAMON is opted-in for DAMON patches scanning [1] and email delivery [2]. > > Clarify how that could be used on DAMON maintainer profile. > > > > [1] https://github.com/sashiko-dev/sashiko/commit/ad9f4a98f958 > > [2] https://github.com/sashiko-dev/sashiko/commit/b554c7b6e733 > > > > Signed-off-by: SeongJae Park <sj@kernel.org> > > --- > > Documentation/mm/damon/maintainer-profile.rst | 21 +++++++++++++++++++ > > 1 file changed, 21 insertions(+) > > > > diff --git a/Documentation/mm/damon/maintainer-profile.rst b/Documentation/mm/damon/maintainer-profile.rst > > index bcb9798a27a86..5c23b1281c50c 100644 > > --- a/Documentation/mm/damon/maintainer-profile.rst > > +++ b/Documentation/mm/damon/maintainer-profile.rst > > @@ -100,3 +100,24 @@ There is also a public Google `calendar > > <https://calendar.google.com/calendar/u/0?cid=ZDIwOTA4YTMxNjc2MDQ3NTIyMmUzYTM5ZmQyM2U4NDA0ZGIwZjBiYmJlZGQxNDM0MmY4ZTRjOTE0NjdhZDRiY0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t>`_ > > that has the events. Anyone can subscribe to it. DAMON maintainer will also > > provide periodic reminders to the mailing list (damon@lists.linux.dev). > > + > > +AI Review > > +--------- > > + > > +For patches that are publicly posted to DAMON mailing list > > +(damon@lists.linux.dev), AI reviews of the patches will be available at > > +sashiko.dev. The reviews could also be sent as mails to the author of the > > +patch. > > + > > +Patch authors are encouraged to check the AI reviews and share their opinions. > > +The sharing could be done as a reply to the mail thread. Consider reducing the > > +recipients list for such sharing, since some people are not really interested > > +in AI reviews. As a rule of thumb, drop individuals except DAMON maintainer > > +and stable@vger.kernel.org from the recipients list. > > + > > +`hkml` also provides a `feature > > +<https://github.com/sjp38/hackermail/blob/master/USAGE.md#forwarding-sashikodev-statuscomments-to-mailing-list>`_ > > +for such sharing. Please feel free to use the feature. > > + > > +It is only a non-mandastory recommendation. DAMON maintainer could also ask > > non-mandatory Good eyes! Thank you, Randy. I use Google doc for typo checks, but seems the use of "-" made Google doc not to complain this. > or maybe > This is an optional recommendation. Sounds better, I will respin with this, unless Andrew picks this patch with the change. Thanks, SJ [...]
© 2016 - 2026 Red Hat, Inc.