From: Theodore Tso <tytso@MIT.EDU>
To: David Miller <davem@davemloft.net>
Cc: aneesh.kumar@linux.vnet.ibm.com, cmm@us.ibm.com,
akpm@linux-foundation.org, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] sparc: Export needed symbol for ZERO_PAGE usage in modules.
Date: Mon, 24 Mar 2008 17:08:39 -0400 [thread overview]
Message-ID: <20080324210839.GF18661@mit.edu> (raw)
In-Reply-To: <20080324.133445.229184630.davem@davemloft.net>
On Mon, Mar 24, 2008 at 01:34:45PM -0700, David Miller wrote:
> From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
> Date: Mon, 24 Mar 2008 23:32:57 +0530
>
> > ext4 use ZERO_PAGE(0) to zero out blocks. We need to export
> > different symbols in different arch for the usage of ZERO_PAGE
> > in modules.
> >
> > Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
>
> Merge this in with the necessary ext4 changes, and no
> sooner.
This is something we plan to merge in the next 2.6.26 merge window,
which is presumably soon. Stephen Rothwell picked this up as a
problem on the linux-next tree, when he tried to build ext4 as a
module on the Power architecture, and it's a problem on sparc as well.
We could merge this in the ext4-tree, but Andrew tends to get cranky
when we put patches which affect code outside of ext4 in the ext4
patchset.
We're happy to carry the patch in the ext4 tree, with an Acked-by with
you, and push it to Linus ourselves, if that's OK with everyone. Or
we can push it to each individual architecture tree, which is what I
thought was considered the preferred practice.
Regards,
- Ted
next prev parent reply other threads:[~2008-03-24 21:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-24 18:02 [PATCH] sparc: Export needed symbol for ZERO_PAGE usage in modules Aneesh Kumar K.V
2008-03-24 20:34 ` David Miller
2008-03-24 21:08 ` Theodore Tso [this message]
2008-03-24 21:44 ` David Miller
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=20080324210839.GF18661@mit.edu \
--to=tytso@mit.edu \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=cmm@us.ibm.com \
--cc=davem@davemloft.net \
--cc=linux-ext4@vger.kernel.org \
/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