From: "Theodore Ts'o" <tytso@mit.edu>
To: Eryu Guan <eguan@redhat.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH 2/2] Drop _require_fssum
Date: Mon, 22 May 2017 11:35:33 -0400 [thread overview]
Message-ID: <20170522153533.4xoavbkheotrmyml@thunk.org> (raw)
In-Reply-To: <20170522144749.GU7250@eguan.usersys.redhat.com>
On Mon, May 22, 2017 at 10:47:49PM +0800, Eryu Guan wrote:
> I think this is still needed. It has FSSUM_PROG definition (otherwise
> all these btrfs tests failed due to unable to find $FSSUM_PROG), and we
> do check for existence of binary files in src, even the file is built
> unconditionally on make. They can be removed accidently or one may
> forget to build a newly added test.
Good point; I had missed that.
- Ted
next prev parent reply other threads:[~2017-05-22 15:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 1:05 [PATCH 1/2] Stop relying on OpenSSL Theodore Ts'o
2017-05-22 1:05 ` [PATCH 2/2] Drop _require_fssum Theodore Ts'o
2017-05-22 14:47 ` Eryu Guan
2017-05-22 15:35 ` Theodore Ts'o [this message]
2017-05-25 17:41 ` [PATCH] Stop relying on OpenSSL Theodore Ts'o
2017-05-22 14:38 ` [PATCH 1/2] " 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=20170522153533.4xoavbkheotrmyml@thunk.org \
--to=tytso@mit.edu \
--cc=eguan@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