From: Dave Chinner <david@fromorbit.com>
To: "Lukáš Czerner" <lczerner@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Eric Whitney <enwlinux@gmail.com>,
linux-ext4@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [PATCH 1/3] xfstests: add helper for zero range support check
Date: Tue, 22 Apr 2014 19:46:12 +1000 [thread overview]
Message-ID: <20140422094612.GJ18672@dastard> (raw)
In-Reply-To: <alpine.LFD.2.00.1404221127240.7437@localhost.localdomain>
On Tue, Apr 22, 2014 at 11:28:31AM +0200, Lukáš Czerner wrote:
> On Tue, 22 Apr 2014, Christoph Hellwig wrote:
>
> > Date: Tue, 22 Apr 2014 02:16:20 -0700
> > From: Christoph Hellwig <hch@infradead.org>
> > To: Dave Chinner <david@fromorbit.com>
> > Cc: Christoph Hellwig <hch@infradead.org>, linux-ext4@vger.kernel.org,
> > xfs@oss.sgi.com, Eric Whitney <enwlinux@gmail.com>
> > Subject: Re: [PATCH 1/3] xfstests: add helper for zero range support check
> >
> > On Tue, Apr 22, 2014 at 07:14:43PM +1000, Dave Chinner wrote:
> > > I don't really care either way, as long as all the checks are done
> > > consistently. Send a patch to change them all... :)
> >
> > My flink test already avoids the wrapper :)
> >
> > So how about we stop adding them for now at least.
>
> I agree,
>
> even though I screwed up when using _require_xfs_io_command with
> fzero :) I think that we can avoid the wrappers and just use
> _require_xfs_io_command() with the command name.
Send patches ;)
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2014-04-22 9:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-21 20:40 [PATCH 1/3] xfstests: add helper for zero range support check Eric Whitney
2014-04-22 6:28 ` Christoph Hellwig
2014-04-22 9:14 ` Dave Chinner
2014-04-22 9:16 ` Christoph Hellwig
2014-04-22 9:28 ` Lukáš Czerner
2014-04-22 9:46 ` 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=20140422094612.GJ18672@dastard \
--to=david@fromorbit.com \
--cc=enwlinux@gmail.com \
--cc=hch@infradead.org \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=xfs@oss.sgi.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).