From: Juntong Deng <juntong.deng@outlook.com>
To: sj@kernel.org, shuah@kernel.org
Cc: damon@lists.linux.dev, linux-mm@kvack.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: [PATCH] selftests/damon: Add executable permission to test scripts
Date: Tue, 26 Sep 2023 04:35:52 +0800 [thread overview]
Message-ID: <VI1P193MB07529234393616AE94D58C7B99FCA@VI1P193MB0752.EURP193.PROD.OUTLOOK.COM> (raw)
When running the test for the damon subsystem, there are a lot of
warnings because test scripts do not have executable permission,
for example:
Warning: file debugfs_attrs.sh is not executable
Warning: file debugfs_schemes.sh is not executable
Warning: file debugfs_target_ids.sh is not executable
...
This patch adds executable permission to test scripts to eliminate
these warnings.
Signed-off-by: Juntong Deng <juntong.deng@outlook.com>
---
tools/testing/selftests/damon/debugfs_attrs.sh | 0
.../testing/selftests/damon/debugfs_duplicate_context_creation.sh | 0
tools/testing/selftests/damon/debugfs_empty_targets.sh | 0
tools/testing/selftests/damon/debugfs_huge_count_read_write.sh | 0
tools/testing/selftests/damon/debugfs_rm_non_contexts.sh | 0
tools/testing/selftests/damon/debugfs_schemes.sh | 0
tools/testing/selftests/damon/debugfs_target_ids.sh | 0
tools/testing/selftests/damon/lru_sort.sh | 0
tools/testing/selftests/damon/reclaim.sh | 0
tools/testing/selftests/damon/sysfs.sh | 0
tools/testing/selftests/damon/sysfs_update_removed_scheme_dir.sh | 0
11 files changed, 0 insertions(+), 0 deletions(-)
mode change 100644 => 100755 tools/testing/selftests/damon/debugfs_attrs.sh
mode change 100644 => 100755 tools/testing/selftests/damon/debugfs_duplicate_context_creation.sh
mode change 100644 => 100755 tools/testing/selftests/damon/debugfs_empty_targets.sh
mode change 100644 => 100755 tools/testing/selftests/damon/debugfs_huge_count_read_write.sh
mode change 100644 => 100755 tools/testing/selftests/damon/debugfs_rm_non_contexts.sh
mode change 100644 => 100755 tools/testing/selftests/damon/debugfs_schemes.sh
mode change 100644 => 100755 tools/testing/selftests/damon/debugfs_target_ids.sh
mode change 100644 => 100755 tools/testing/selftests/damon/lru_sort.sh
mode change 100644 => 100755 tools/testing/selftests/damon/reclaim.sh
mode change 100644 => 100755 tools/testing/selftests/damon/sysfs.sh
mode change 100644 => 100755 tools/testing/selftests/damon/sysfs_update_removed_scheme_dir.sh
diff --git a/tools/testing/selftests/damon/debugfs_attrs.sh b/tools/testing/selftests/damon/debugfs_attrs.sh
old mode 100644
new mode 100755
diff --git a/tools/testing/selftests/damon/debugfs_duplicate_context_creation.sh b/tools/testing/selftests/damon/debugfs_duplicate_context_creation.sh
old mode 100644
new mode 100755
diff --git a/tools/testing/selftests/damon/debugfs_empty_targets.sh b/tools/testing/selftests/damon/debugfs_empty_targets.sh
old mode 100644
new mode 100755
diff --git a/tools/testing/selftests/damon/debugfs_huge_count_read_write.sh b/tools/testing/selftests/damon/debugfs_huge_count_read_write.sh
old mode 100644
new mode 100755
diff --git a/tools/testing/selftests/damon/debugfs_rm_non_contexts.sh b/tools/testing/selftests/damon/debugfs_rm_non_contexts.sh
old mode 100644
new mode 100755
diff --git a/tools/testing/selftests/damon/debugfs_schemes.sh b/tools/testing/selftests/damon/debugfs_schemes.sh
old mode 100644
new mode 100755
diff --git a/tools/testing/selftests/damon/debugfs_target_ids.sh b/tools/testing/selftests/damon/debugfs_target_ids.sh
old mode 100644
new mode 100755
diff --git a/tools/testing/selftests/damon/lru_sort.sh b/tools/testing/selftests/damon/lru_sort.sh
old mode 100644
new mode 100755
diff --git a/tools/testing/selftests/damon/reclaim.sh b/tools/testing/selftests/damon/reclaim.sh
old mode 100644
new mode 100755
diff --git a/tools/testing/selftests/damon/sysfs.sh b/tools/testing/selftests/damon/sysfs.sh
old mode 100644
new mode 100755
diff --git a/tools/testing/selftests/damon/sysfs_update_removed_scheme_dir.sh b/tools/testing/selftests/damon/sysfs_update_removed_scheme_dir.sh
old mode 100644
new mode 100755
--
2.39.2
next reply other threads:[~2023-09-25 20:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 20:35 Juntong Deng [this message]
2023-09-25 20:53 ` 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=VI1P193MB07529234393616AE94D58C7B99FCA@VI1P193MB0752.EURP193.PROD.OUTLOOK.COM \
--to=juntong.deng@outlook.com \
--cc=damon@lists.linux.dev \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shuah@kernel.org \
--cc=sj@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