From: Randy Dunlap <randy.dunlap@oracle.com>
To: coly.li@suse.de
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: mmotm 2009-03-23-22-34 uploaded (reiserfs)
Date: Wed, 25 Mar 2009 08:07:12 -0700 [thread overview]
Message-ID: <49CA48A0.6000404@oracle.com> (raw)
In-Reply-To: <49C9C163.8040502@suse.de>
Coly Li wrote:
> Hi Randy,
>
> Randy Dunlap Wrote:
>> akpm@linux-foundation.org wrote:
>>> The mm-of-the-moment snapshot 2009-03-23-22-34 has been uploaded to
>>>
>>> http://userweb.kernel.org/~akpm/mmotm/
>>>
>>> and will soon be available at
>>>
>>> git://git.zen-sources.org/zen/mmotm.git
>>>
>>> It contains the following patches against 2.6.29-rc8:
>>
>>> fs-reiserfs-return-f_fsid-for-statfs2-v2.patch
>> fs/built-in.o: In function `reiserfs_statfs':
>> super.c:(.text+0x7332b): undefined reference to `crc32_le'
>> super.c:(.text+0x7333f): undefined reference to `crc32_le'
>>
> Hmm, it should not be. The v2 patch includes linux/crc32.h, and I tested without
> any error. Now I am downloading mmotm to verify.
CONFIG_CRC32=m
Since reiserfs is built into the kernel image (CONFIG_REISERFS=y),
CONFIG_CRC32 also needs to be =y.
Probably just add
select CRC32
select BITREVERSE
to the REISERFS_FS kconfig entry.
> BTW, from series file of mmotm, I see two version patches,
> fs-reiserfs-return-f_fsid-for-statfs2.patch
> fs-reiserfs-return-f_fsid-for-statfs2-v2.patch
> are all included. I suspect whether this is a proper behavior.
The v2 patch mostly replaces the first one. I don't see a
problem with them.
--
~Randy
next prev parent reply other threads:[~2009-03-25 15:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200903240539.n2O5d6A8018954@imap1.linux-foundation.org>
2009-03-24 20:53 ` mmotm 2009-03-23-22-34 uploaded (reiserfs) Randy Dunlap
2009-03-25 5:30 ` Coly Li
2009-03-25 15:07 ` Randy Dunlap [this message]
2009-03-25 16:51 ` Coly Li
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=49CA48A0.6000404@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=coly.li@suse.de \
--cc=linux-kernel@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