From: SJ Park <sj@kernel.org>
To: Manuel Ebner <manuelebnerli@mailbox.org>
Cc: SJ Park <sj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Adrian Huang (Lenovo)" <adrianhuang0701@gmail.com>,
damon@lists.linux.dev, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/damon: fix typo and grammar
Date: Fri, 9 Oct 2026 01:18:16 -0700 [thread overview]
Message-ID: <20261009081816.41705-1-sj@kernel.org> (raw)
In-Reply-To: <20261008162010.4010682-2-manuelebnerli@mailbox.org>
Hello Manuel,
Let's use "mm/damon/reclaim:" as the subject prefix.
On Thu, 8 Oct 2026 18:20:10 +0200 Manuel Ebner <manuelebnerli@mailbox.org> wrote:
> DAMON_RCLAIM -> DAMON_RECLAIM
> set as -> set to
>
> Signed-off-by: Manuel Ebner <manuelebnerli@mailbox.org>
> CC: Adrian Huang (Lenovo) <adrianhuang0701@gmail.com>
Other than the subject prefix,
Reviewed-by: SJ Park <sj@kernel.org>
> ---
> I hope I got the right git-tree. somehow there's 'damon/next'
> and 'damon/next/damon/next'
> The other patches will take a couple more days.
mm-new is the recommended baseline for now. It might change in future. Please
refer to this document [1] for more details.
I applied this patch to damon/next [1] tree after changing the subject prefix
to what I suggested. We are now quite close to next merge window. It may
better to focus on making mm.git more stabilized and therefore ready for the
next merge window, rather than adding more changes that are not really urgent.
I understand this series is not really urgent. Hence, Andrew might not add
this patch until next -rc1 release. In the case, I will request adding this to
mm.git after next -rc1 release. So, no action from your side is needed for
now. Let me know if you think this is really urgent.
[1] https://origin.kernel.org/doc/html/latest/mm/damon/maintainer-profile.html#scm-trees
Thanks,
SJ
[...]
prev parent reply other threads:[~2026-10-09 8:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 16:20 [PATCH] mm/damon: fix typo and grammar Manuel Ebner
2026-10-08 16:25 ` sashiko-bot
2026-10-09 2:54 ` Enze Li
2026-10-09 8:18 ` 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=20261009081816.41705-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=adrianhuang0701@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=manuelebnerli@mailbox.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