From: Chao Yu <chao@kernel.org>
To: Zorro Lang <zlang@kernel.org>,
fstests@vger.kernel.org, Joanne Chang <joannechien@google.com>
Cc: chao@kernel.org, Jaegeuk Kim <jaegeuk@kernel.org>,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH v1 2/3] f2fs/016: add test cases for test_dummy_encryption mount option
Date: Fri, 14 Nov 2025 09:33:58 +0800 [thread overview]
Message-ID: <98034c77-5e47-43ea-9c45-335e2cd51b68@kernel.org> (raw)
In-Reply-To: <20251112135223.3467852-2-joannechien@google.com>
On 11/12/2025 9:52 PM, Joanne Chang wrote:
> Add test cases to verify f2fs's support for different versions of the
> "test_dummy_encryption" mount option.
>
> To ensure test robustness, the MKFS_OPTIONS and MOUNT_OPTIONS are
> cleared. This prevents additional options from interfereing with the
> test results.
>
> Signed-off-by: Joanne Chang <joannechien@google.com>
To Zorro,
The changes look good to me, though, still I want to confirm that whether
it is recommended or not to add new cases in old testcase.
Thanks,
next prev parent reply other threads:[~2025-11-14 1:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 13:52 [PATCH v1 1/3] f2fs/015: clear MKFS_OPTIONS and MOUNT_OPTIONS Joanne Chang
2025-11-12 13:52 ` [PATCH v1 2/3] f2fs/016: add test cases for test_dummy_encryption mount option Joanne Chang
2025-11-14 1:33 ` Chao Yu [this message]
2025-11-15 6:49 ` Zorro Lang
2025-11-15 10:57 ` Chao Yu
2025-11-12 13:52 ` [PATCH v1 3/3] f2fs/{019,020}: clear MOUNT_OPTIONS alongside MKFS_OPTIONS Joanne Chang
2025-11-14 1:34 ` Chao Yu
2025-11-14 1:30 ` [PATCH v1 1/3] f2fs/015: clear MKFS_OPTIONS and MOUNT_OPTIONS Chao Yu
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=98034c77-5e47-43ea-9c45-335e2cd51b68@kernel.org \
--to=chao@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=jaegeuk@kernel.org \
--cc=joannechien@google.com \
--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