From: SJ Park <sj@kernel.org>
To: Liew Rui Yan <aethernet65535@gmail.com>
Cc: SJ Park <sj@kernel.org>,
akpm@linux-foundation.org, corbet@lwn.net, damon@lists.linux.dev,
david@kernel.org, liam@infradead.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org, ljs@kernel.org,
mhocko@suse.com, rppt@kernel.org, skhan@linuxfoundation.org,
surenb@google.com, vbabka@kernel.org
Subject: Re: [PATCH 0/3] docs/mm/damon/design: add explanation of nr_snapshots
Date: Tue, 11 Aug 2026 20:07:32 -0700 [thread overview]
Message-ID: <20260812030733.8996-1-sj@kernel.org> (raw)
In-Reply-To: <20260811170252.32705-1-aethernet65535@gmail.com>
On Wed, 12 Aug 2026 01:02:52 +0800 Liew Rui Yan <aethernet65535@gmail.com> wrote:
> Hi SJ,
>
>
> On Tue, 11 Aug 2026 06:56:53 -0700 SJ Park <sj@kernel.org> wrote:
>
> > Hi Liew,
> >
> >
> > 'hkml patch check' [1] says you forgot Cc-ing below people who are recommended
> > by get_maintainer.pl. Please Cc all recipients who
> > get_maitnainer.pl is recommending, from the next time. 'hkml patch format' [2]
> > could also help you doing so.
> >
>
> Thank you for reminding me! I will CC all email addresses output by
> get_maitnainer.pl from the next time.
>
> > [...]
> >
> > On Tue, 11 Aug 2026 18:18:38 +0800 Liew Rui Yan <aethernet65535@gmail.com> wrote:
> >
> > > Add an explanation of nr_snapshots to avoid misunderstandings.
> >
> > Thank you for this patch series, Liew.
> >
> > >
> > > Liew Rui Yan (3):
> > > docs/mm/damon/design: accurate semantics of nr_snapshots
> > > docs/mm/damon/design: difference between watermarks and nr_snapshots
> > > docs/mm/damon/design: fix typo of max_nr_snapshots
> >
> > I requested changes to patches 1 and 2 via replies.
>
> I will make changes in the next revision:
>
> patch-1: "tried to be __completely applied__" -> "__completely tried__
> to be applied".
>
> patch-2: use two spaces between sentences.
Sounds good!
>
> >
> > [1] https://github.com/sjp38/hackermail/blob/master/USAGE.md#checking-patches
> > [2] https://github.com/sjp38/hackermail/blob/master/USAGE.md#formatting-patches
>
>
> Best regards,
> Rui Yan
Thanks,
SJ
prev parent reply other threads:[~2026-08-12 3:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 10:18 [PATCH 0/3] docs/mm/damon/design: add explanation of nr_snapshots Liew Rui Yan
2026-08-11 10:18 ` [PATCH 1/3] docs/mm/damon/design: accurate semantics " Liew Rui Yan
2026-08-11 13:46 ` SJ Park
2026-08-11 17:01 ` Liew Rui Yan
2026-08-11 10:18 ` [PATCH 2/3] docs/mm/damon/design: difference between watermarks and nr_snapshots Liew Rui Yan
2026-08-11 13:48 ` SJ Park
2026-08-11 10:18 ` [PATCH 3/3] docs/mm/damon/design: fix typo of max_nr_snapshots Liew Rui Yan
2026-08-11 13:52 ` SJ Park
2026-08-11 13:56 ` [PATCH 0/3] docs/mm/damon/design: add explanation of nr_snapshots SJ Park
2026-08-11 17:02 ` Liew Rui Yan
2026-08-12 3:07 ` SJ 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=20260812030733.8996-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=aethernet65535@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=damon@lists.linux.dev \
--cc=david@kernel.org \
--cc=liam@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox