From: SJ Park <sj@kernel.org>
To: SJ Park <sj@kernel.org>
Cc: Song Hu <husong@kylinos.cn>,
damon@lists.linux.dev, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>,
Lorenzo Stoakes <ljs@kernel.org>,
"Liam R. Howlett" <liam@infradead.org>,
Vlastimil Babka <vbabka@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>
Subject: Re: [PATCH 0/4] Docs/ABI/damon: sysfs ABI document fixes and additions
Date: Fri, 10 Jul 2026 07:28:12 -0700 [thread overview]
Message-ID: <20260710142812.25332-1-sj@kernel.org> (raw)
In-Reply-To: <20260710141631.24657-1-sj@kernel.org>
On Fri, 10 Jul 2026 07:16:38 -0700 SJ Park <sj@kernel.org> wrote:
[...]
> On Fri, 10 Jul 2026 12:47:33 +0800 Song Hu <husong@kylinos.cn> wrote:
>
> > This series fixes typos and fills in missing entries in the DAMON
> > sysfs ABI document (Documentation/ABI/testing/sysfs-kernel-mm-damon).
> >
> > Patch 1 fixes a path typo, "intrvals_goal" -> "intervals_goal", in
> > four What: entries; the documented path points to a non-existent
> > directory, so it is Cc'ed to stable.
> >
> > Patch 2 fixes two further typos ("WDate:", "manimum").
> >
> > Patches 3 and 4 add ABI entries that exist in the kernel and are
> > already described in usage.rst but are missing from the canonical ABI
> > document: the 'update_tuned_intervals' state command (patch 3) and the
> > 'tried_regions/<R>/probes/<P>/hits' file (patch 4).
>
> Looks good overall. Patch 3 looks unnecessary, though. Let me add comments to
> each patch.
Sorry, I was misreading patch 3. All patches including the third one looks
good to me now.
This series is applied to damon/next [1] tree. If this series is not added to
mm.git in short term (~1 week?), I will ask mm.git maintainer (Andrew Morton)
to pick this. So, no action from your side is needed for now. If it seems I
also forgot doing that or you cannot wait for my action, please feel free to
directly ask that to Andrew.
[1] https://origin.kernel.org/doc/html/latest/mm/damon/maintainer-profile.html#scm-trees
Thanks,
SJ
[...]
prev parent reply other threads:[~2026-07-10 14:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 4:47 [PATCH 0/4] Docs/ABI/damon: sysfs ABI document fixes and additions Song Hu
2026-07-10 4:47 ` [PATCH 1/4] Docs/ABI/damon: fix typo in intervals_goal sysfs path Song Hu
2026-07-10 14:17 ` SJ Park
2026-07-11 0:21 ` SJ Park
2026-07-11 5:04 ` Song Hu
2026-07-10 4:47 ` [PATCH 2/4] Docs/ABI/damon: fix typos Song Hu
2026-07-10 14:18 ` SJ Park
2026-07-10 4:47 ` [PATCH 3/4] Docs/ABI/damon: document update_tuned_intervals state command Song Hu
2026-07-10 14:24 ` SJ Park
2026-07-10 4:47 ` [PATCH 4/4] Docs/ABI/damon: document tried_regions probe hits Song Hu
2026-07-10 14:25 ` SJ Park
2026-07-10 14:16 ` [PATCH 0/4] Docs/ABI/damon: sysfs ABI document fixes and additions SJ Park
2026-07-10 14:28 ` 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=20260710142812.25332-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--cc=david@kernel.org \
--cc=husong@kylinos.cn \
--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=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