From: SeongJae Park <sj@kernel.org>
To: Swaraj Gaikwad <swarajgaikwad1925@gmail.com>
Cc: SeongJae Park <sj@kernel.org>,
akpm@linux-foundation.org, damon@lists.linux.dev,
david.hunter.linux@gmail.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, skhan@linuxfoundation.org
Subject: Re: [PATCH v2] mm/damon/sysfs-schemes: Remove outdated TODO in target_nid_store()
Date: Wed, 10 Dec 2025 13:49:39 -0800 [thread overview]
Message-ID: <20251210214939.62774-1-sj@kernel.org> (raw)
In-Reply-To: <20251211030707.16417-2-swarajgaikwad1925@gmail.com>
On Thu, 11 Dec 2025 03:07:08 +0000 Swaraj Gaikwad <swarajgaikwad1925@gmail.com> wrote:
> The TODO comment in target_nid_store() suggested adding range validation
> for target_nid. As discussed in [1], the current behavior of accepting
> any integer value is intentional. DAMON sysfs aims to remain flexible,
> including supporting users who prepare node IDs before future NUMA hotplug
> events.
>
> Because this behavior matches the broader design philosophy of the DAMON
> sysfs interface, the TODO comment is now misleading. This patch removes the
> comment.
Thank you so much for this patch, Swaraj!
You sent this as a reply to v1. In mm/ and damon/ subsystems, we prefer new
versions of patches to be sent as a new email, rather than a reply to the
previous version. Please consider doing so next time.
>
> No functional changes.
>
> [1] https://lore.kernel.org/lkml/20251210150930.57679-1-sj@kernel.org/
This kind of link is useful for tracking the history. Thank you for adding
this.
>
> v2:
> - Removed the logic changes (validation) introduced in v1.
> - Updated commit message to reflect that only the comment is being removed.
This kind of change history should be placed under the '---' line [1] below.
Please consider doing so next time.
>
> Suggested-by: SeongJae Park <sj@kernel.org>
> Signed-off-by: Swaraj Gaikwad <swarajgaikwad1925@gmail.com>
Other than the trivial comments above, change looks good to me.
Reviewed-by: SeongJae Park <sj@kernel.org>
If you willing to, please address the comments and send v3. Because the
comments are for only very trivial things, if you don't or can't do that in
days, I will address those and send it as v3 on my own.
[1] https://docs.kernel.org/process/submitting-patches.html#commentary
Thanks,
SJ
[...]
prev parent reply other threads:[~2025-12-10 21:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-10 11:17 [PATCH] mm/damon/sysfs: check for online node in target_nid_store Swaraj Gaikwad
2025-12-10 15:09 ` SeongJae Park
2025-12-11 3:07 ` [PATCH v2] mm/damon/sysfs-schemes: Remove outdated TODO in target_nid_store() Swaraj Gaikwad
2025-12-10 21:49 ` SeongJae 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=20251210214939.62774-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--cc=david.hunter.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=skhan@linuxfoundation.org \
--cc=swarajgaikwad1925@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).