From: David Sterba <dsterba@suse.com>
To: fstests@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>
Subject: [PATCH] btrfs: use full subcommand names
Date: Thu, 30 Mar 2017 17:06:33 +0200 [thread overview]
Message-ID: <20170330150633.14962-1-dsterba@suse.com> (raw)
Update the remaining calls to 'btrfs' that use shortened command names.
Use of full names is recommended to avoid any ambiguities.
Signed-off-by: David Sterba <dsterba@suse.com>
---
tests/btrfs/027 | 2 +-
tests/btrfs/085 | 6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/tests/btrfs/027 b/tests/btrfs/027
index 46970a2918a7..2c8b458e5ff4 100755
--- a/tests/btrfs/027
+++ b/tests/btrfs/027
@@ -78,7 +78,7 @@ run_test()
_scratch_mount >>$seqres.full 2>&1
local missing_dev=`echo $SCRATCH_DEV_POOL | awk '{print $2}'`
- local missing_dev_id=`$BTRFS_UTIL_PROG fi show $SCRATCH_MNT | grep $missing_dev | awk '{print $2}'`
+ local missing_dev_id=`$BTRFS_UTIL_PROG filesystem show $SCRATCH_MNT | grep $missing_dev | awk '{print $2}'`
# get some data on the filesystem so there's something to replace
_ddt of="$SCRATCH_MNT"/file1 bs=1M count=1 >> $seqres.full 2>&1
diff --git a/tests/btrfs/085 b/tests/btrfs/085
index 3dbc67f5d40b..804899724cba 100755
--- a/tests/btrfs/085
+++ b/tests/btrfs/085
@@ -134,14 +134,14 @@ test_orphan()
new_subvolume()
{
- _run_btrfs_util_prog subvol create $SCRATCH_MNT/testdir
+ _run_btrfs_util_prog subvolume create $SCRATCH_MNT/testdir
}
new_default()
{
new_subvolume
- SUB=$($BTRFS_UTIL_PROG subvol list $SCRATCH_MNT |awk '{print $2}')
- _run_btrfs_util_prog subvol set-default $SUB $SCRATCH_MNT
+ SUB=$($BTRFS_UTIL_PROG subvolume list $SCRATCH_MNT |awk '{print $2}')
+ _run_btrfs_util_prog subvolume set-default $SUB $SCRATCH_MNT
_unmount_flakey
_mount_flakey
--
2.12.0
reply other threads:[~2017-03-30 15:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170330150633.14962-1-dsterba@suse.com \
--to=dsterba@suse.com \
--cc=fstests@vger.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