From: Dave Chinner <david@fromorbit.com>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Cc: Eryu Guan <eguan@redhat.com>,
fstests@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v5] fstests: btrfs: Add reserved space leak check for rewrite dirty page
Date: Thu, 27 Aug 2015 11:14:22 +1000 [thread overview]
Message-ID: <20150827011422.GH3902@dastard> (raw)
In-Reply-To: <55DD68E8.2020702@cn.fujitsu.com>
On Wed, Aug 26, 2015 at 03:21:12PM +0800, Qu Wenruo wrote:
> Eryu Guan wrote on 2015/08/26 14:41 +0800:
> >Just one minor issue here, please remove $seqres.full before test,
> >otherwise $seqres.full will keep growing.
>
> Oh, you're right.
> I did forgot to remove it.
>
> BTW, is it better to add 'rm $seqres.full' to the template?
Yes, that's a good idea. Separate patch, though. ;)
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2015-08-27 1:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 1:17 [PATCH v5] fstests: btrfs: Add reserved space leak check for rewrite dirty page Qu Wenruo
2015-08-26 6:41 ` Eryu Guan
2015-08-26 7:21 ` Qu Wenruo
2015-08-27 1:14 ` Dave Chinner [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=20150827011422.GH3902@dastard \
--to=david@fromorbit.com \
--cc=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).