From: Andrew Morton <akpm@linux-foundation.org>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com,
cluster-devel@redhat.com, samba-technical@lists.samba.org,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH] zero_user_page conversion
Date: Sat, 23 Jun 2007 09:51:57 -0700 [thread overview]
Message-ID: <20070623095157.5a574afb.akpm@linux-foundation.org> (raw)
In-Reply-To: <4679A558.1010107@redhat.com>
> On Wed, 20 Jun 2007 17:08:24 -0500 Eric Sandeen <sandeen@redhat.com> wrote:
> Use zero_user_page() in cifs, ocfs2, ext4, and gfs2 where possible.
One patch, splattered across four maintainers, each of whom maintain separate
trees.
Sigh. Please, don't. _someone_ has to split this up, and it might as well
not be me.
<splits it up>
prev parent reply other threads:[~2007-06-23 16:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-20 22:08 [PATCH] zero_user_page conversion Eric Sandeen
2007-06-21 0:21 ` Mark Fasheh
2007-06-23 16:51 ` Andrew Morton [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=20070623095157.5a574afb.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=cluster-devel@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ocfs2-devel@oss.oracle.com \
--cc=samba-technical@lists.samba.org \
--cc=sandeen@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 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).