From: Zach Brown <zach.brown@oracle.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
mark.fasheh@oracle.com, Joel Becker <Joel.Becker@oracle.com>
Subject: Re: [Patch] add AOP_TRUNCATED_PAGE, prepend AOP_ to WRITEPAGE_ACTIVATE
Date: Fri, 04 Nov 2005 10:31:35 -0800 [thread overview]
Message-ID: <436BA907.9080604@oracle.com> (raw)
In-Reply-To: <20051103205802.31121fc4.akpm@osdl.org>
> So for both -mm and for the ocfs2 team, leaving the patch in the ocfs2 git
> tree is the most convenient place for it.
Well, I don't think it matters much either way because we mostly test by
checking out of svn and buliding against -mm or patched distro kernels. I'd
leave the details up to you and Joel (who maintains our ocfs2 git) -- whatever
is easiest for you guys.
> Obviously, merging it into Linus's tree will fix up everyone's patching
> problems, but it has no users at this time...
So, speaking of which, are there any barriers to merging OCFS2 now? I think
Christoph's concerns (silly /proc files, vma walking, endian stuff) have been
addressed.
- z
next prev parent reply other threads:[~2005-11-04 18:31 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
2005-11-04 4:58 ` Andrew Morton
2005-11-04 18:31 ` Zach Brown [this message]
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=436BA907.9080604@oracle.com \
--to=zach.brown@oracle.com \
--cc=Joel.Becker@oracle.com \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.fasheh@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 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.