From: Eric Biggers <ebiggers@google.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] [xfstests-bld] kvm-xfstests: forbid conflicting specifications of FSTESTCFG
Date: Fri, 21 Oct 2016 13:55:18 -0700 [thread overview]
Message-ID: <20161021205518.GC137744@google.com> (raw)
In-Reply-To: <20160930222158.hlqvupjhdibjhiht@thunk.org>
On Fri, Sep 30, 2016 at 06:21:58PM -0400, Theodore Ts'o wrote:
> On Fri, Sep 23, 2016 at 01:56:12PM -0700, Eric Biggers wrote:
> > It was possible to run kvm-xfstests with arguments like '-c encrypt
> > smoke', in which case FSTESTCFG ended up set to "4k" because 'smoke'
> > implies '-c 4k' and the second config specification overrode the first.
> > If the user tries something like this, fail with a helpful error message
> > rather than proceeding with a configuration that likely wasn't intended.
> >
> > Signed-off-by: Eric Biggers <ebiggers@google.com>
>
> Applie,d thanks.
>
> - Ted
Hi Ted,
Are you planning to push out new commits to the public xfstests-bld repository?
Thanks,
Eric
next prev parent reply other threads:[~2016-10-21 20:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 20:56 [PATCH] [xfstests-bld] Remove redundant gce-xfstests documentation Eric Biggers
2016-09-23 20:56 ` [PATCH] [xfstests-bld] Fix typos in xfstests-bld documentation Eric Biggers
2016-09-30 22:21 ` Theodore Ts'o
2016-09-23 20:56 ` [PATCH] [xfstests-bld] kvm-xfstests: forbid conflicting specifications of FSTESTCFG Eric Biggers
2016-09-30 22:21 ` Theodore Ts'o
2016-10-21 20:55 ` Eric Biggers [this message]
2016-10-21 21:37 ` Theodore Ts'o
2016-09-30 22:19 ` [PATCH] [xfstests-bld] Remove redundant gce-xfstests documentation Theodore Ts'o
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=20161021205518.GC137744@google.com \
--to=ebiggers@google.com \
--cc=fstests@vger.kernel.org \
--cc=tytso@mit.edu \
/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