From: Eryu Guan <guaneryu@gmail.com>
To: Christoph Hellwig <hch@lst.de>
Cc: fstests@vger.kernel.org, jlayton@kernel.org
Subject: Re: [PATCH] xfstests: remove generic/484
Date: Sun, 1 Mar 2020 22:32:26 +0800 [thread overview]
Message-ID: <20200301143222.GL3840@desktop> (raw)
In-Reply-To: <20200224222926.694991-1-hch@lst.de>
On Mon, Feb 24, 2020 at 02:29:26PM -0800, Christoph Hellwig wrote:
> Generic/484 tests functionality that isn't really related to file
> systems, and has failed every since it was added. Remove it as it
> serves no puropse in xfstests.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
I also removed src/t_locks_execve.c which is used only by this test, and
its entries in src/Makefile & .gitignore file.
Thanks,
Eryu
prev parent reply other threads:[~2020-03-01 14:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 22:29 [PATCH] xfstests: remove generic/484 Christoph Hellwig
2020-02-24 22:37 ` Darrick J. Wong
2020-02-26 7:50 ` Zorro Lang
2020-02-26 15:22 ` Murphy Zhou
2020-03-01 14:32 ` Eryu Guan [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=20200301143222.GL3840@desktop \
--to=guaneryu@gmail.com \
--cc=fstests@vger.kernel.org \
--cc=hch@lst.de \
--cc=jlayton@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;
as well as URLs for NNTP newsgroup(s).