[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4AF4B259.8030506@oracle.com>
Date: Fri, 06 Nov 2009 15:33:45 -0800
From: Randy Dunlap <randy.dunlap@...cle.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
CC: linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
Catalin Marinas <catalin.marinas@....com>
Subject: [PATCH -next] kmemleak: fix kconfig for crc32 build error
From: Randy Dunlap <randy.dunlap@...cle.com>
kmemleak uses crc32 functions so it needs to select CRC32.
Fixes build error:
kmemleak.c:(.text+0x7ce62): undefined reference to `crc32_le'
Signed-off-by: Randy Dunlap <randy.dunlap@...cle.com>
Cc: Catalin Marinas <catalin.marinas@....com>
---
lib/Kconfig.debug | 1 +
1 file changed, 1 insertion(+)
--- linux-next-20091106.orig/lib/Kconfig.debug
+++ linux-next-20091106/lib/Kconfig.debug
@@ -372,6 +372,7 @@ config DEBUG_KMEMLEAK
select DEBUG_FS if SYSFS
select STACKTRACE if STACKTRACE_SUPPORT
select KALLSYMS
+ select CRC32
help
Say Y here if you want to enable the memory leak
detector. The memory allocation/freeing is traced in a way
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists