Re: -mm merge plans for 2.6.23 -- sys_fallocate

[Amit K. Arora]

On Tue, Jul 10, 2007 at 11:20:47AM -0700, Mark Fasheh wrote:
> On Tue, Jul 10, 2007 at 11:45:03AM -0400, Theodore Tso wrote:
> > On Tue, Jul 10, 2007 at 02:22:13AM -0700, Andrew Morton wrote:
> > > On Tue, 10 Jul 2007 11:07:37 +0200 Heiko Carstens <heiko.carstens@xxxxxxxxxx> wrote:
> > > > We reserved a different syscall number than the one that is used right now
> > > > in the patch. Please drop this patch... Martin or I will wire up the syscall
> > > > as soon as the x86 variant is merged. Everything else just causes trouble and
> > > > confusion.
> > > 
> > > OK, I dropped all the fallocate patches.
> > 
> > Andrew, I want to clarify who is going to push the fallocate patches.
> > I can either push them to Linus as part of the ext4 patch set, or we
> > can wait for you to push them.  I thought since you had them in -mm
> > and we were going to wait you to push them (and presume that this was
> > going to happen soon).
> > 
> > Alternatively I can push them directly to Linus along with other ext4
> > patches.  We can drop the s390 patch if Martin or Heiko wants to wire
> > it up themselves.
> > 
> > As far as I know there hasn't been any real contention on the actual
> > syscall patches, other than the numbering issues, so it seems that
> > pushing them to Linus sooner rather than later is the right thing to
> > do. 
> 
> Where is the latest and greatest version of those patches? Is it still the
> patch set distributed in 2.6.22-rc6-mm1? I'd mostly like to see the final
> set of flags we're planning on supporting. But yeah, I second the "sooner
> rather than later" :)

I have posted the latest fallocate patches as part of TAKE6. These
patches are exactly same as how they currently look in the ext4 patch
queue being maintained by Ted.

--
Regards,
Amit Arora
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/