From: SJ Park <sj@kernel.org>
To: sashiko-bot@kernel.org
Cc: SJ Park <sj@kernel.org>, "Shuah Khan" <shuah@kernel.org>,
damon@lists.linux.dev, linux-mm@kvack.org
Subject: Re: [RFC PATCH v2 6/6] selftests/damon: remove unused imports of os and sys modules
Date: Sun, 1 Nov 2026 09:38:36 -0800 [thread overview]
Message-ID: <20261101173837.82868-1-sj@kernel.org> (raw)
In-Reply-To: <sashiko-outbox-192521@kernel.org>
On Sun, 01 Nov 2026 17:20:33 +0000 sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Low] selftests/damon: commit subject names wrong removed modules
> --
>
> commit dfc99fb0f6f595e8bf824229e67f0b391cab2a8e
> Author: SJ Park <sj@kernel.org>
>
> selftests/damon: remove unused imports of os and sys modules
>
> This commit removes unused Python module imports from
> sysfs_no_op_commit_break.py and sysfs_update_schemes_tried_regions_hang.py
> in the DAMON selftests.
>
> > selftests/damon: remove unused imports of os and sys modules
> >
> > sysfs_no_op_commit_break.py imports 'sys' module but never uses it.
> > sysfs_update_schemes_tried_regions_hang imports 'time' module but never
> > uses it. Remove the unnecessary imports.
> >
> > The issue is found using flake8.
> >
> > Signed-off-by: SJ Park <sj@kernel.org>
>
> [Severity: Low]
> As reported by Sashiko on RFC [1], should the commit subject be updated to
> refer to the sys and time modules instead of os and sys?
Yes, I forgot updating the subject. I will do in the next spin.
>
> In tools/testing/selftests/damon/sysfs_no_op_commit_break.py, the patch
> removes import sys while import os remains and is used in
> dump_damon_status_dict():
>
> file_dir = os.path.dirname(os.path.abspath(__file__))
> dump_script = os.path.join(file_dir, 'drgn_dump_damon_status.py')
>
> In tools/testing/selftests/damon/sysfs_update_schemes_tried_regions_hang.py,
> the patch removes import time while both import os and import sys remain and
> are used at module scope:
>
> sys.path.append(os.path.dirname(os.path.abspath(__file__)))
>
> [1] https://lore.kernel.org/r/sashiko-outbox-192115@kernel.org
>
> --
> Sashiko AI review · https://sashiko.dev/#/patchset/20261101171630.81477-1-sj@kernel.org?part=6
>
Thanks,
SJ
prev parent reply other threads:[~2026-11-01 17:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-01 17:16 [RFC PATCH v2 0/6] mm/damon: misc improvements/cleanups for core, vaddr, sysfs and tests SJ Park
2026-11-01 17:16 ` [RFC PATCH v2 1/6] mm/damon/vaddr: advance migration attempt in folio level for filter out SJ Park
2026-11-01 17:16 ` [RFC PATCH v2 2/6] mm/damon/vaddr: use damos->last_applied for migrate action SJ Park
2026-11-01 17:27 ` sashiko-bot
2026-11-01 17:33 ` SJ Park
2026-11-01 17:16 ` [RFC PATCH v2 3/6] mm/damon/vaddr: implement sz_filter_passed for migrate_{hot,cold} action SJ Park
2026-11-01 17:21 ` sashiko-bot
2026-11-01 17:37 ` SJ Park
2026-11-01 17:16 ` [RFC PATCH v2 4/6] mm/damon/sysfs-schemes: drop redundant and racy zero target_value check SJ Park
2026-11-01 17:16 ` [RFC PATCH v2 5/6] selftests/damon/damos_apply_interval: remove unused variables SJ Park
2026-11-01 17:16 ` [RFC PATCH v2 6/6] selftests/damon: remove unused imports of os and sys modules SJ Park
2026-11-01 17:20 ` sashiko-bot
2026-11-01 17:38 ` 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=20261101173837.82868-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=damon@lists.linux.dev \
--cc=linux-mm@kvack.org \
--cc=sashiko-bot@kernel.org \
--cc=shuah@kernel.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