From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] ext4-new-features: Fix paths to ffsb-config files
Date: Wed, 9 Oct 2019 09:47:16 +0200 [thread overview]
Message-ID: <20191009074716.GA601@dell5510> (raw)
In-Reply-To: <20191009062112.49947-1-lkml@jv-coder.de>
Hi Joerg,
> The path to the ffsb-config files was just plain wrong (they are copied to
> $LTPROOT/testcases/data/ext4-ffsb, but searched in cwd.
> This is the same fix as in 4ae5699d, only for other tests.
> Signed-off-by: Joerg Vehlow <joerg.vehlow@aox-tech.de>
> ---
> .../ext4-journal-checksum/ext4_journal_checksum.sh | 2 +-
> .../ext4-uninit-groups/ext4_uninit_groups_test.sh | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
Thanks for your patch.
ext4_online_defrag_test.sh still contains wrong path.
I'd prefer to introduce some variable in ext4_funcs.sh, e.g.:
FFSB_CONFIG_DIR="$LTPROOT/testcases/data/ext4-ffsb"
Kind regards,
Petr
prev parent reply other threads:[~2019-10-09 7:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 6:21 [LTP] [PATCH] ext4-new-features: Fix paths to ffsb-config files Joerg Vehlow
2019-10-09 7:47 ` Petr Vorel [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=20191009074716.GA601@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