From: Manuel Ebner <manuelebnerli@mailbox.org>
To: Aveline Noir <jm5905938@gmail.com>, SJ Park <sj@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
damon@lists.linux.dev, linux-mm@kvack.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/8] Docs/admin-guide/mm/damon/start: fix grammar
Date: Mon, 26 Oct 2026 13:41:32 +0100 [thread overview]
Message-ID: <b0d8d0ceda82e303262c0f61324fe8a84fd9f745.camel@mailbox.org> (raw)
In-Reply-To: <179301327249.2.1796164575094900927.damon-docs-grammar-1@gmail.com>
On Mon, 2026-10-26 at 22:14 +1100, Aveline Noir wrote:
> Fix a few grammar slips in the getting-started guide, like "make DAMON
> monitors" and a region "that has not accessed".
>
> "The line of the commands" used to be "The first two lines". With only
> one masim line left, I make it "The first line".
>
> Signed-off-by: Aveline Noir <jm5905938@gmail.com>
> ---
> Documentation/admin-guide/mm/damon/start.rst | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/admin-guide/mm/damon/start.rst b/Documentation/admin-guide/mm/damon/start.rst
> index d98b0eb8e771..a83fcc2265bd 100644
> --- a/Documentation/admin-guide/mm/damon/start.rst
> +++ b/Documentation/admin-guide/mm/damon/start.rst
> @@ -63,7 +63,7 @@ the execution. ::
>
> The first command of the above example downloads and builds an artificial
> memory access generator program called ``masim``. The second command asks DAMO
> -to start the program via the given command and make DAMON monitors the newly
> +to start the program via the given command and make DAMON monitor the newly
'The second command asks ... and makes ...' Thus:
+to start the program via the given command and makes DAMON monitor the newly
> started process. The third command retrieves the current snapshot of the
> monitored access pattern of the process from DAMON and shows the pattern in a
> human readable format.
> @@ -71,7 +71,7 @@ human readable format.
> The first line of the output shows the relative access temperature (hotness) of
> the regions in a single row heatmap format. Each column on the heatmap
> represents regions of same size on the monitored virtual address space. The
> -position of the column on the row and the number on the column represents the
> +position of the column on the row and the number on the column represent the
> relative location and access temperature of the region. ``[...]`` means
> unmapped huge regions on the virtual address spaces. The second line shows
> additional information for better understanding the heatmap.
I have read the damon directory aswell but I didn't find enought to send a patch yet.
But I found this, could you add it to your patch?
@@ -78,8 +78,8 @@ additional information for better understanding the heatmap.
Each line of the output from the third line shows which virtual address range
(``addr XX size XX``) of the process is how frequently (``access XX %``)
-accessed for how long time (``age XX``). For example, the eleventh region of
-~9.5 MiB size is being most frequently accessed for last 3.7 seconds. Finally,
+accessed for how long (``age XX``). For example, the eleventh region of
+~9.5 MiB size is being most frequently accessed for the last 3.7 seconds. Finally,
the fourth command stops DAMON.
Rest looks good to me:
Reviewed-by: Manuel Ebner <manuelebnerli@mailbox.org>
Thanks
> ...
next prev parent reply other threads:[~2026-10-26 12:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 11:14 [PATCH 0/8] Docs: damon: fix grammar and typos Aveline Noir
2026-10-26 11:14 ` [PATCH 1/8] Docs/admin-guide/mm/damon/start: fix grammar Aveline Noir
2026-10-26 12:41 ` Manuel Ebner [this message]
2026-10-26 14:29 ` SJ Park
2026-10-26 15:50 ` Aveline Noir
2026-10-26 14:10 ` SJ Park
2026-10-26 11:14 ` [PATCH 2/8] Docs/admin-guide/mm/damon/stat: fix pronoun agreement Aveline Noir
2026-10-26 12:44 ` Manuel Ebner
2026-10-26 14:31 ` SJ Park
2026-10-26 15:50 ` Aveline Noir
2026-10-26 14:24 ` SJ Park
2026-10-26 11:14 ` [PATCH 3/8] Docs/admin-guide/mm/damon/usage: fix grammar Aveline Noir
2026-10-26 14:37 ` SJ Park
2026-10-26 11:14 ` [PATCH 4/8] Docs/admin-guide/mm/damon/lru_sort: fix remaining grammar Aveline Noir
2026-10-26 12:57 ` Manuel Ebner
2026-10-26 14:44 ` SJ Park
2026-10-26 15:50 ` Aveline Noir
2026-10-26 14:42 ` SJ Park
2026-10-26 11:14 ` [PATCH 5/8] Docs/mm/damon/design: fix grammar and typos Aveline Noir
2026-10-26 14:54 ` SJ Park
2026-10-26 11:14 ` [PATCH 6/8] Docs/mm/damon/api: fix verb form Aveline Noir
2026-10-26 14:55 ` SJ Park
2026-10-26 11:14 ` [PATCH 7/8] Docs/mm/damon/maintainer-profile: fix subject-verb agreement Aveline Noir
2026-10-26 14:56 ` SJ Park
2026-10-26 11:14 ` [PATCH 8/8] Docs/mm/damon/monitoring_intervals_tuning_example: fix grammar and typos Aveline Noir
2026-10-26 14:59 ` SJ Park
2026-10-27 0:49 ` [PATCH 0/8] Docs: damon: " SJ Park
2026-10-27 2:46 ` Aveline Noir
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=b0d8d0ceda82e303262c0f61324fe8a84fd9f745.camel@mailbox.org \
--to=manuelebnerli@mailbox.org \
--cc=corbet@lwn.net \
--cc=damon@lists.linux.dev \
--cc=jm5905938@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rdunlap@infradead.org \
--cc=sj@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
all inboxes | Powered by JetHome®