From: Eryu Guan <eguan@redhat.com>
To: Wang Xiaoguang <wangxg.fnst@cn.fujitsu.com>
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] generic: create and delete files repeatedly to exercise ENOSPC behaviour
Date: Wed, 2 Nov 2016 18:36:56 +0800 [thread overview]
Message-ID: <20161102103655.GW27776@eguan.usersys.redhat.com> (raw)
In-Reply-To: <5819BE82.10205@cn.fujitsu.com>
On Wed, Nov 02, 2016 at 06:22:58PM +0800, Wang Xiaoguang wrote:
> hi Eryu,
>
> There has already be a generic/102 doing this test...
> Thanks for you kindly review and sorry for wasting your time.
I had impression yesterday that we have a case that does exactly the
same test, and I searched but didn't find it.. It turns out that we do
have it already :)
Thanks for writing new test cases!
Eryu
next prev parent reply other threads:[~2016-11-02 10:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 11:19 [PATCH] generic: create and delete files repeatedly to exercise ENOSPC behaviour Wang Xiaoguang
2016-11-01 12:26 ` Eryu Guan
2016-11-02 10:22 ` Wang Xiaoguang
2016-11-02 10:36 ` Eryu Guan [this message]
2016-11-02 1:27 ` Dave Chinner
2016-11-02 10:24 ` Wang Xiaoguang
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=20161102103655.GW27776@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=wangxg.fnst@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.