From: Chao Yu <chao@kernel.org>
To: Eryu Guan <guaneryu@gmail.com>, Chao Yu <yuchao0@huawei.com>
Cc: fstests@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH 1/2] check: recognize f2fs through parameter
Date: Sun, 7 Oct 2018 21:51:48 +0800 [thread overview]
Message-ID: <05f43b5d-0e67-ba87-63dd-e45e8bd4c371@kernel.org> (raw)
In-Reply-To: <20181006093207.GI17817@desktop>
On 2018-10-6 17:32, Eryu Guan wrote:
> On Sun, Sep 30, 2018 at 05:26:52PM +0800, Chao Yu wrote:
>> Add a paramenter in check to configure $FSTYP for f2fs.
>>
>> Signed-off-by: Chao Yu <yuchao0@huawei.com>
>> ---
>> check | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/check b/check
>> index f3c8021d94b9..a9024094721a 100755
>> --- a/check
>> +++ b/check
>> @@ -59,6 +59,7 @@ check options
>> -pvfs2 test PVFS2
>> -tmpfs test TMPFS
>> -ubifs test ubifs
>> + -f2fs test f2fs
>> -l line mode diff
>> -udiff show unified diff (default)
>> -n show me, do not run tests
>> @@ -263,6 +264,7 @@ while [ $# -gt 0 ]; do
>> -pvfs2) FSTYP=pvfs2 ;;
>> -tmpfs) FSTYP=tmpfs ;;
>> -ubifs) FSTYP=ubifs ;;
>> + -f2fs) FSTYP=f2fs ;;
>
> The test harness should be able to detect the f2fs type from $TEST_DEV.
> We add param to set FSTYP only when there's no way to tell the
> filesystem type from the device.
Hi Eryu,
Okay, thanks for the explanation, let's just ignore this patch.
Thanks,
>
> Thanks,
> Eryu
>
>>
>> -g) group=$2 ; shift ;
>> GROUP_LIST="$GROUP_LIST ${group//,/ }"
>> --
>> 2.18.0.rc1
>>
prev parent reply other threads:[~2018-10-07 13:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-30 9:26 [PATCH 1/2] check: recognize f2fs through parameter Chao Yu
2018-09-30 9:26 ` [PATCH 2/2] common/quota: adapt _require_prjquota() for f2fs Chao Yu
2018-10-06 9:32 ` [PATCH 1/2] check: recognize f2fs through parameter Eryu Guan
2018-10-07 13:51 ` Chao Yu [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=05f43b5d-0e67-ba87-63dd-e45e8bd4c371@kernel.org \
--to=chao@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=guaneryu@gmail.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=yuchao0@huawei.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).