From: Christoph Hellwig <hch@infradead.org>
To: Zach Brown <zach.brown@oracle.com>
Cc: Andrew Morton <akpm@osdl.org>,
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, 4 Nov 2005 20:59:14 +0000 [thread overview]
Message-ID: <20051104205914.GA11202@infradead.org> (raw)
In-Reply-To: <436BA907.9080604@oracle.com>
On Fri, Nov 04, 2005 at 10:31:35AM -0800, Zach Brown wrote:
> > 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.
I think it's in pretty good shape now. The stuct typedefs should go before
we put it in mainline so we don't need to do a major sweep through everything
just after it appeared in SCM history, but that's just a minor thingy.
Else I'd say it looks good unless we see problems with the AOP_TRUNCATED_PAGE
patch we should send it to linus after the time for the big core merges is
over (aka in about a week or two)
next prev parent reply other threads:[~2005-11-04 20:59 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
2005-11-04 18:37 ` Wim Coekaerts
2005-11-04 20:59 ` Christoph Hellwig [this message]
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=20051104205914.GA11202@infradead.org \
--to=hch@infradead.org \
--cc=Joel.Becker@oracle.com \
--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 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.