From: Eric Sandeen <sandeen@redhat.com>
To: "Amit K. Arora" <aarora@linux.vnet.ibm.com>
Cc: Nick Piggin <npiggin@suse.de>, Andreas Dilger <adilger@sun.com>,
Eelis <opensuse.org@contacts.eelis.net>,
Theodore Ts'o <tytso@mit.edu>,
Nikanth Karthikesan <knikanth@suse.de>,
coly.li@suse.de, Amit Arora <aarora@in.ibm.com>,
xfs@oss.sgi.com, Christoph Hellwig <hch@infradead.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH v2] New testcase to check if fallocate respects RLIMIT_FSIZE or not
Date: Wed, 05 May 2010 10:50:07 -0500 [thread overview]
Message-ID: <4BE193AF.3070505@redhat.com> (raw)
In-Reply-To: <20100505075556.GA5142@amitarora.in.ibm.com>
On 05/05/2010 02:55 AM, Amit K. Arora wrote:
> On Tue, May 04, 2010 at 03:44:08PM -0500, Eric Sandeen wrote:
>> Amit K. Arora wrote:
>>> Here is the new testcase.
>> Thanks! A few comments...
> Thanks for the review!
Sure thing - looks good, I'll merge it after a retest if it all goes
well. :)
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2010-05-05 15:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201004281854.49730.knikanth@suse.de>
[not found] ` <4BD85F1F.7030100@suse.de>
[not found] ` <201004291014.07194.knikanth@suse.de>
[not found] ` <20100430143319.d51d6d77.akpm@linux-foundation.org>
[not found] ` <20100501070426.GA9562@amitarora.in.ibm.com>
[not found] ` <20100501101846.GA3769@infradead.org>
2010-05-03 8:31 ` [PATCH] New testcase to check if fallocate respects RLIMIT_FSIZE or not Amit K. Arora
2010-05-04 20:44 ` Eric Sandeen
2010-05-05 7:55 ` [PATCH v2] " Amit K. Arora
2010-05-05 15:50 ` Eric Sandeen [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=4BE193AF.3070505@redhat.com \
--to=sandeen@redhat.com \
--cc=aarora@in.ibm.com \
--cc=aarora@linux.vnet.ibm.com \
--cc=adilger@sun.com \
--cc=akpm@linux-foundation.org \
--cc=coly.li@suse.de \
--cc=hch@infradead.org \
--cc=knikanth@suse.de \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=opensuse.org@contacts.eelis.net \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--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