From: Andrew Morton <akpm@linux-foundation.org>
To: Mark Fasheh <mark.fasheh@oracle.com>
Cc: aarora@in.ibm.com, linux-fsdevel@vger.kernel.org,
ocfs2-devel@oss.oracle.com
Subject: Re: [-mm PATCH] ocfs2: ->fallocate() support
Date: Sat, 23 Jun 2007 09:54:15 -0700 [thread overview]
Message-ID: <20070623095415.6fba0f73.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070621190143.GC17713@ca-server1.us.oracle.com>
> On Thu, 21 Jun 2007 12:01:43 -0700 Mark Fasheh <mark.fasheh@oracle.com> wrote:
> Plug ocfs2 into the ->fallocate() callback. We only support FA_ALLOCATE for
> now - FA_DEALLOCATE will come later.
I get a healthy reject when applying this against your own tree. Perhaps
because my copy of it is a few days old, dunno.
I think I'll duck it, allow you to merge this in the normal fashion once
fallocate hits mainline, OK?
next prev parent reply other threads:[~2007-06-23 16:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 19:01 [-mm PATCH] ocfs2: ->fallocate() support Mark Fasheh
2007-06-23 16:54 ` Andrew Morton [this message]
2007-06-23 17:24 ` Mark Fasheh
2007-06-30 9:34 ` Christoph Hellwig
2007-07-02 23:18 ` Mark Fasheh
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=20070623095415.6fba0f73.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=aarora@in.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mark.fasheh@oracle.com \
--cc=ocfs2-devel@oss.oracle.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).