From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH ltp] runtest/{ltplite, stress.part1}: update commands for gf01-30/rwtest01-05
Date: Thu, 26 Jul 2018 15:04:39 +0200 [thread overview]
Message-ID: <20180726130439.GA12339@dell5510> (raw)
In-Reply-To: <20180706084928.6017-1-yixin.zhang@intel.com>
Hi Yixin,
> gf01-30/rwtest01-05 are orignal defined in runtest file 'fs', and they
> are updated multiple times in file 'fs' but missed in 'ltplite'/'stress.part1'.
> So this patch copy all updates to the tests in 'ltplite'/'stress.part1'.
> Ref:
> c9dd96e6b2f811dbad119c3558d90cb7dfc3919b
> 95e8b61433efcefb83699aaf859e92ad2b576373
> 606e544932248858f65c7ab3061f77c542c07cfe
> Signed-off-by: Yixin Zhang <yixin.zhang@intel.com>
I wonder if we want to keep these runtest/stress.part[1-3] and runtest/ltplite
files. ATM we don't have feature to include runtest files (among other problems
with test runner), but keeping this duplicity doesn't look to me.
Kind regards,
Petr
next prev parent reply other threads:[~2018-07-26 13:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 8:49 [LTP] [PATCH ltp] runtest/{ltplite, stress.part1}: update commands for gf01-30/rwtest01-05 Yixin Zhang
2018-07-26 13:04 ` Petr Vorel [this message]
2018-07-30 13:08 ` Jan Stancek
2018-08-15 6:54 ` Zhang, Yixin
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=20180726130439.GA12339@dell5510 \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
/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