From: Mark Fasheh <mark.fasheh@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Nick Piggin <npiggin@suse.de>,
Steven Whitehouse <swhiteho@redhat.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: + fs-introduce-write_begin-write_end-and-perform_write-aops.patch added to -mm tree
Date: Wed, 30 May 2007 15:44:43 -0700 [thread overview]
Message-ID: <20070530224443.GP20632@ca-server1.us.oracle.com> (raw)
In-Reply-To: <20070529202441.749fb402.akpm@linux-foundation.org>
On Tue, May 29, 2007 at 08:24:41PM -0700, Andrew Morton wrote:
> hm, I suppose that means I need to undrop git-ocfs2.patch. It has a mild
> disagreeement with the fault-vs-invalidate patches which I didn't feel like
> fixing.
Erf, somehow I missed that it was dropped. I guess I'll take a look...
--Mark
--
Mark Fasheh
Senior Software Developer, Oracle
mark.fasheh@oracle.com
next prev parent reply other threads:[~2007-05-30 22:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 21:19 + fs-introduce-write_begin-write_end-and-perform_write-aops.patch added to -mm tree akpm
2007-05-30 3:13 ` Nick Piggin
2007-05-30 3:24 ` Andrew Morton
2007-05-30 22:44 ` Mark Fasheh [this message]
2007-05-30 22:49 ` Andrew Morton
2007-05-30 10:39 ` Steven Whitehouse
2007-05-31 5:50 ` Nick Piggin
2007-06-13 13:40 ` Dmitriy Monakhov
2007-06-13 11:43 ` Nick Piggin
2007-06-13 18:51 ` Dmitriy Monakhov
2007-06-13 23:07 ` Badari Pulavarty
2007-06-13 23:28 ` Nick Piggin
2007-06-14 9:52 ` Jan Kara
2007-06-14 10:39 ` Nick Piggin
2007-06-13 13:50 ` [patch] new aop block_write_begin fix Dmitriy Monakhov
2007-06-13 13:57 ` iov_iter_fault_in_readable fix Dmitriy Monakhov
2007-06-14 17:31 ` Christoph Hellwig
2007-06-14 22:21 ` David Chinner
2007-06-14 22:34 ` Christoph Hellwig
2007-06-16 18:17 ` Dmitriy Monakhov
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=20070530224443.GP20632@ca-server1.us.oracle.com \
--to=mark.fasheh@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=swhiteho@redhat.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 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.