public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Zorro Lang <zlang@redhat.com>
To: fstests@vger.kernel.org
Cc: Zorro Lang <zlang@redhat.com>
Subject: [PATCH] xfs/299: change variable name from "temp" to "tmp" for typo error
Date: Thu, 14 Apr 2016 13:32:23 +0800	[thread overview]
Message-ID: <1460611943-14660-1-git-send-email-zlang@redhat.com> (raw)

In xfs/299, project IDs are in $tmp.projid file. But there's one
line code try to use $temp.projid. Fortunately, it doesn't bring
any problems until now, but if keep using $temp.projid it really
don't make sense.

Signed-off-by: Zorro Lang <zlang@redhat.com>
---

Hi,

When I found xfs/299 run failed, I try to dig into it. Although
I sent a duplicate patch for XFS, but there's another tiny
problem I found when I check xfs/299 failure.

I know this problem is very potty, so if someone is writting
another patch about xfs/299, you can fix this incidentally.

Thanks,
Zorro

 tests/xfs/299 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tests/xfs/299 b/tests/xfs/299
index 1f61eea..d2670f8 100755
--- a/tests/xfs/299
+++ b/tests/xfs/299
@@ -143,7 +143,7 @@ _exercise()
 	_file_as_id $SCRATCH_MNT/initme $id $type 1024 0
 	echo "ls -l $SCRATCH_MNT" >>$seqres.full
 	ls -l $SCRATCH_MNT >>$seqres.full
-	xfs_quota -D $tmp.projects -P $temp.projid -x \
+	xfs_quota -D $tmp.projects -P $tmp.projid -x \
 		-c "limit -$type bsoft=${bsoft}k bhard=${bhard}k $id" \
 		-c "limit -$type isoft=$isoft ihard=$ihard $id" \
 		$SCRATCH_DEV
-- 
2.5.5


             reply	other threads:[~2016-04-14  5:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-14  5:32 Zorro Lang [this message]
2016-04-14  6:49 ` [PATCH] xfs/299: change variable name from "temp" to "tmp" for typo error Eryu Guan

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=1460611943-14660-1-git-send-email-zlang@redhat.com \
    --to=zlang@redhat.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