From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: Zorro Lang <zlang@redhat.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [Patch V2] ext4-new-features: modify ext4_get_inode_version.sh not know $EXT4_DEV definition
Date: Thu, 23 Oct 2014 08:18:11 +0800 [thread overview]
Message-ID: <54484943.30601@cn.fujitsu.com> (raw)
In-Reply-To: <1413983374-8784-1-git-send-email-zlang@redhat.com>
On 10/22/2014 09:09 PM, Zorro Lang wrote:
> ext4_get_inode_version.sh use $EXT4_DEV, but it really doesn't know what is $EXT4_DEV.
> That cause other cases which use ext4_get_inode_version.sh to fail.
Applied, thank you.
Wanlong Gao
>
> Signed-off-by: Zorro Lang <zlang@redhat.com>
> ---
> testcases/kernel/fs/ext4-new-features/ext4_funcs.sh | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/testcases/kernel/fs/ext4-new-features/ext4_funcs.sh b/testcases/kernel/fs/ext4-new-features/ext4_funcs.sh
> index 0ae534a..b51e942 100755
> --- a/testcases/kernel/fs/ext4-new-features/ext4_funcs.sh
> +++ b/testcases/kernel/fs/ext4-new-features/ext4_funcs.sh
> @@ -45,7 +45,7 @@ ext4_setup()
> if [ -z "$LTP_BIG_DEV" ];then
> tst_brkm TCONF "tests need a big block device(5G-10G)"
> else
> - EXT4_DEV=$LTP_BIG_DEV
> + export EXT4_DEV=$LTP_BIG_DEV
> fi
>
> tst_tmpdir
>
------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2014-10-23 0:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 13:09 [LTP] [Patch V2] ext4-new-features: modify ext4_get_inode_version.sh not know $EXT4_DEV definition Zorro Lang
2014-10-23 0:18 ` Wanlong Gao [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=54484943.30601@cn.fujitsu.com \
--to=gaowanlong@cn.fujitsu.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=zlang@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.