From: Christoph Hellwig <hch@lst.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: fallocate, Re: -mm merge plans for 2.6.23
Date: Wed, 11 Jul 2007 14:00:37 +0200 [thread overview]
Message-ID: <20070711120037.GE18665@lst.de> (raw)
In-Reply-To: <20070710013152.ef2cd200.akpm@linux-foundation.org>
> fallocate-implementation-on-i86-x86_64-and-powerpc.patch
> fallocate-on-s390.patch
> fallocate-on-ia64.patch
> fallocate-on-ia64-fix.patch
>
> Merge.
Hopefull this will be done during the 2.6.23 merge window, but right now
it's not (yet).
next prev parent reply other threads:[~2007-07-11 12:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070710013152.ef2cd200.akpm@linux-foundation.org>
2007-07-11 11:35 ` -mm merge plans for 2.6.23 Christoph Hellwig
2007-07-11 11:39 ` David Woodhouse
2007-07-11 17:21 ` Andrew Morton
2007-07-11 17:28 ` Randy Dunlap
2007-07-11 12:00 ` Christoph Hellwig [this message]
[not found] ` <46957BE1.1010104@yahoo.com.au>
2007-07-12 2:31 ` block_page_mkwrite? (Re: fault vs invalidate race (Re: -mm merge plans for 2.6.23)) David Chinner
2007-07-12 2:42 ` Nick Piggin
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=20070711120037.GE18665@lst.de \
--to=hch@lst.de \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).