From: SeongJae Park <sj@kernel.org>
To: SeongJae Park <sj@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
David Hildenbrand <david@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Lorenzo Stoakes <ljs@kernel.org>, Michal Hocko <mhocko@suse.com>,
Mike Rapoport <rppt@kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>,
Suren Baghdasaryan <surenb@google.com>,
Vlastimil Babka <vbabka@kernel.org>,
damon@lists.linux.dev, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: (sashiko review) [PATCH] Docs/mm/damon/maintainer-profile: add AI review usage guideline
Date: Sat, 11 Apr 2026 11:51:35 -0700 [thread overview]
Message-ID: <20260411185136.82032-1-sj@kernel.org> (raw)
In-Reply-To: <20260411184802.81804-1-sj@kernel.org>
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
[...]
prev parent reply other threads:[~2026-04-11 18:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-11 17:49 [PATCH] Docs/mm/damon/maintainer-profile: add AI review usage guideline SeongJae Park
2026-04-11 18:27 ` Randy Dunlap
2026-04-11 18:30 ` SeongJae Park
2026-04-11 18:48 ` (sashiko review) " SeongJae Park
2026-04-11 18:51 ` 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=20260411185136.82032-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=damon@lists.linux.dev \
--cc=david@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=surenb@google.com \
--cc=vbabka@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 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.