From: SeongJae Park <sj@kernel.org>
To: Enze Li <lienze@kylinos.cn>
Cc: SeongJae Park <sj@kernel.org>,
akpm@linux-foundation.org, damon@lists.linux.dev,
linux-mm@kvack.org, enze.li@gmx.com
Subject: Re: [PATCH] mm/damon: rename primitives to operations
Date: Mon, 26 May 2025 11:09:21 -0700 [thread overview]
Message-ID: <20250526180921.2932-1-sj@kernel.org> (raw)
In-Reply-To: <87o6vfj3bv.fsf@kylinos.cn>
On Mon, 26 May 2025 14:25:40 +0800 Enze Li <lienze@kylinos.cn> wrote:
> Hi SeongJae,
>
> On Sat, May 24 2025 at 09:29:10 AM -0700, SeongJae Park wrote:
[...]
> >
> > Could you please revise as abovely suggested and resend?
>
> I've sent a v2 to the current thread,
I think it is more common to send new versions of a patch as a new thread,
rather than as a reply to an old version. Please do so from next time, for a
consistency.
> many thanks for your review and
> suggestions! Please let me know if further adjustments are needed.
David gave us good point[1] to think about the title. I don't think that's a
strict blocker, but also no reason to rush on this. So let's take a bit more
time for the discussion, unless this is urgent for you.
[1] https://lore.kernel.org/dc5391f3-6e0a-4e6a-b319-0c602af29202@redhat.com
Thanks,
SJ
[...]
next prev parent reply other threads:[~2025-05-26 18:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-24 12:55 Enze Li
2025-05-24 16:29 ` SeongJae Park
2025-05-26 6:25 ` Enze Li
2025-05-26 18:09 ` SeongJae Park [this message]
2025-05-30 1:57 ` Enze Li
2025-05-26 9:31 ` David Hildenbrand
2025-05-26 17:55 ` SeongJae Park
2025-05-29 17:26 ` SeongJae Park
2025-05-30 5:47 ` Enze Li
2025-05-26 6:09 ` [PATCH v2] mm/damon: fix outdated comments for monitoring primitives Enze Li
2025-05-26 18:12 ` SeongJae Park
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=20250526180921.2932-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--cc=enze.li@gmx.com \
--cc=lienze@kylinos.cn \
--cc=linux-mm@kvack.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