From: Chao Yu <chao@kernel.org>
To: Zorro Lang <zlang@kernel.org>, fstests@vger.kernel.org
Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
Chao Yu <chao@kernel.org>
Subject: [PATCH 1/3] common/config: source common/f2fs in _source_specific_fs()
Date: Thu, 9 Oct 2025 16:50:41 +0800 [thread overview]
Message-ID: <20251009085043.16910-1-chao@kernel.org> (raw)
Let's source common/f2fs in _source_specific_fs() instead of in each
testcase.
Cc: Jaegeuk Kim <jaegeuk@kernel.org>
Signed-off-by: Chao Yu <chao@kernel.org>
---
common/config | 1 +
tests/f2fs/002 | 1 -
2 files changed, 1 insertion(+), 1 deletion(-)
diff --git a/common/config b/common/config
index 22b52432..1420e35d 100644
--- a/common/config
+++ b/common/config
@@ -509,6 +509,7 @@ _source_specific_fs()
;;
f2fs)
[ "$MKFS_F2FS_PROG" = "" ] && _fatal "mkfs.f2fs not found"
+ . ./common/f2fs
;;
nfs)
. ./common/nfs
diff --git a/tests/f2fs/002 b/tests/f2fs/002
index 74146217..d2f6e413 100755
--- a/tests/f2fs/002
+++ b/tests/f2fs/002
@@ -43,7 +43,6 @@
_begin_fstest auto quick rw encrypt compress fiemap
. ./common/filter
-. ./common/f2fs
. ./common/encrypt
# Prerequisites to create a file that is both encrypted and LZ4-compressed
--
2.40.1
next reply other threads:[~2025-10-09 9:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 8:50 Chao Yu [this message]
2025-10-09 8:50 ` [PATCH 2/3] common/rc: move _check_f2fs_filesystem() to common/f2fs Chao Yu
2025-10-17 16:21 ` Zorro Lang
2025-10-09 8:50 ` [PATCH 3/3] common/f2fs: introduce _require_inject_f2fs_command() Chao Yu
2025-10-17 16:50 ` Zorro Lang
2025-10-17 16:06 ` [PATCH 1/3] common/config: source common/f2fs in _source_specific_fs() Zorro Lang
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=20251009085043.16910-1-chao@kernel.org \
--to=chao@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=zlang@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