From: Theodore Tso <tytso@mit.edu>
To: Mingming <cmm@us.ibm.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Preparing to push patches for the merge window
Date: Fri, 18 Sep 2009 13:54:24 -0400 [thread overview]
Message-ID: <20090918175424.GG26991@mit.edu> (raw)
In-Reply-To: <1252938276.4920.11.camel@mingming-laptop>
On Mon, Sep 14, 2009 at 07:24:36AM -0700, Mingming wrote:
> On Fri, 2009-09-11 at 17:48 -0400, Theodore Ts'o wrote:
> > See below for a list for what I currently have in the ext4 patch queue.
> >
> > Patches which are NOT yet included are:
> >
> > o Mingming's Fallocate / Direct I/O patches.
> >
> > Mingming, it looked like you were still polishing these two
> > patches?
>
> Yeah, the aio fsync issue is till being working on. I also have some
> issue with using igrab/iput to hold the inode in cache.
Hi Mingming,
Any news on the Direct I/O patches? I pushed a large set of patches
to Linus today, but I'll try to assemble a set of patches that can be
tested and qualified to Linus towards the end of the merge window.
Thanks,
- Ted
prev parent reply other threads:[~2009-09-18 17:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-11 21:48 Preparing to push patches for the merge window Theodore Ts'o
2009-09-14 14:24 ` Mingming
2009-09-18 17:54 ` Theodore Tso [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=20090918175424.GG26991@mit.edu \
--to=tytso@mit.edu \
--cc=cmm@us.ibm.com \
--cc=linux-ext4@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.