public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
	akpm <akpm@linux-foundation•org>
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
	Dave Kleikamp <shaggy@austin•ibm.com>
Subject: [PATCH] jfs: needs crc32_le
Date: Mon, 2 Feb 2009 11:20:55 -0800	[thread overview]
Message-ID: <20090202112055.5ad37047.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20090202201637.28896d2f.sfr@canb.auug.org.au>

From: Randy Dunlap <randy.dunlap@oracle•com>

JFS needs crc32_le(), so select its library config symbol:

fs/built-in.o: In function `jfs_statfs':
super.c:(.text+0x7c8c0): undefined reference to `crc32_le'
super.c:(.text+0x7c8d5): undefined reference to `crc32_le'

Signed-off-by: Randy Dunlap <randy.dunlap@oracle•com>
cc: Dave Kleikamp <shaggy@austin•ibm.com>
---
 fs/jfs/Kconfig |    1 +
 1 file changed, 1 insertion(+)

--- linux-next-20090202.orig/fs/jfs/Kconfig
+++ linux-next-20090202/fs/jfs/Kconfig
@@ -1,6 +1,7 @@
 config JFS_FS
 	tristate "JFS filesystem support"
 	select NLS
+	select CRC32
 	help
 	  This is a port of IBM's Journaled Filesystem .  More information is
 	  available in the file <file:Documentation/filesystems/jfs.txt>.

  parent reply	other threads:[~2009-02-02 19:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-02  9:16 linux-next: Tree for February 2 Stephen Rothwell
     [not found] ` <20090202201637.28896d2f.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2009-02-02 18:34   ` linux-next: Tree for February 2 (iwlwifi) Randy Dunlap
     [not found]     ` <20090202103401.a189e8e0.randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2009-02-02 20:45       ` reinette chatre
2009-02-02 19:20 ` Randy Dunlap [this message]
2009-02-02 19:28   ` [PATCH] jfs: needs crc32_le Dave Kleikamp

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=20090202112055.5ad37047.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle$(echo .)com \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    --cc=shaggy@austin$(echo .)ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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