From: SJ Park <sj@kernel.org>
To: Aveline Noir <jm5905938@gmail.com>
Cc: SJ Park <sj@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
Manuel Ebner <manuelebnerli@mailbox.org>,
damon@lists.linux.dev, linux-mm@kvack.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/8] Docs: damon: fix grammar and typos
Date: Mon, 26 Oct 2026 17:49:15 -0700 [thread overview]
Message-ID: <20261027004916.160854-1-sj@kernel.org> (raw)
In-Reply-To: <179301327249.2.4690198998605536207.damon-docs-grammar-0@gmail.com>
Hello Aveline,
On Mon, 26 Oct 2026 22:14:32 +1100 Aveline Noir <jm5905938@gmail.com> wrote:
> I was reading the DAMON docs and kept running into small grammar
> mistakes and typos, so here is a series that tries to clean them up.
> There is one patch per document, and nothing beyond grammar was
> changed :)
>
> Some fixes pushed lines over 80 columns, so those paragraphs are
> rewrapped. Patch 4 picks up what I think was left in lru_sort.rst
> after Manuel's recent fix.
Thank you for these fixes. All look good to me.
I applied this series to damon/next [1] tree, together with Manuel's
suggestion patches. Manuel's suggestion patches will be squashed into your
original patches while adding 'Suggested-by:' tag for Manuel. I will repost
the resulting version after next -rc1 to request merging of it into the mm.git.
So, no action from your side is needed for now. If anything is wrong or the
plan doesn't work for you, please feel free to let me know.
>
> Based on damon/next at 9d301805e3f6.
Thank you for clarifying the baseline. I guess this was because your patch
depend on Manuel's early lru_sort.rst fix? Clarifying the dependencies would
also be helpful from the next time.
By the way, I found your patches don't have the usual git version signature.
That helped me finding a bug in hkml. I fixed the bug, so no problem.
Nonetheless, I'm just curious. I might be able to make DAMON development
process more easy for contributors if I better understand contributors' work
setup. Are you intentionally removing those suffix, using 'git format-patch
--no-signature' like feature? If so, any reason to do so? This might just
don't matter, though. Please feel free to do not answer if you find no worthy
to answer or just feel uncomfortable.
[1] https://origin.kernel.org/doc/html/latest/mm/damon/maintainer-profile.html#scm-trees
Thanks,
SJ
[...]
next prev parent reply other threads:[~2026-10-27 0:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 11:14 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
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 ` SJ Park [this message]
2026-10-27 2:46 ` [PATCH 0/8] Docs: damon: " 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=20261027004916.160854-1-sj@kernel.org \
--to=sj@kernel.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=manuelebnerli@mailbox.org \
--cc=rdunlap@infradead.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®