From: Christoph Hellwig <hch@infradead.org>
To: Andrew Morton <akpm@osdl.org>, Zach Brown <zach.brown@oracle.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
hch@infradead.org, mark.fasheh@oracle.com
Subject: Re: [Patch] add AOP_TRUNCATED_PAGE, prepend AOP_ to WRITEPAGE_ACTIVATE
Date: Thu, 3 Nov 2005 16:53:06 +0000 [thread overview]
Message-ID: <20051103165306.GA4923@infradead.org> (raw)
In-Reply-To: <20051103074312.GQ11488@ca-server1.us.oracle.com>
On Wed, Nov 02, 2005 at 11:43:12PM -0800, Joel Becker wrote:
> > Looks sane to me. Can you carry this in the ocfs2 tree?
>
> No problem. Give us a day or two to merge the changes to our
> main trees.
I think I disagree with Andew here. Having a core patch separate
from a new drivers/filesystem/etc.. is always a good idea. It makes
reviewing a lot easier and allows independant handling, e.g. merging it
earlier than the new driver for some reason - as happened for example
with the clear_inode changes we needed earlier for ocfs or the pagevec
exports that came in via the reiser4 patches but were needed in mainline
for cifs now.
next prev parent reply other threads:[~2005-11-03 16:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-31 20:05 [Patch] add AOP_TRUNCATED_PAGE, prepend AOP_ to WRITEPAGE_ACTIVATE Zach Brown
2005-11-03 1:45 ` Andrew Morton
2005-11-03 7:43 ` Joel Becker
2005-11-03 16:53 ` Christoph Hellwig [this message]
2005-11-04 4:58 ` Andrew Morton
2005-11-04 18:31 ` Zach Brown
2005-11-04 18:37 ` Wim Coekaerts
2005-11-04 20:59 ` Christoph Hellwig
2005-11-09 8:06 ` Joel Becker
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=20051103165306.GA4923@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.fasheh@oracle.com \
--cc=zach.brown@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).