public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>
Subject: [PATCH -next] kmemleak: fix kconfig for crc32 build error
Date: Fri, 06 Nov 2009 15:33:45 -0800	[thread overview]
Message-ID: <4AF4B259.8030506@oracle.com> (raw)
In-Reply-To: <20091106181330.80bca052.sfr@canb.auug.org.au>

From: Randy Dunlap <randy.dunlap@oracle.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@oracle.com>
Cc: Catalin Marinas <catalin.marinas@arm.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

  reply	other threads:[~2009-11-06 22:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-06  7:13 linux-next: Tree for November 6 Stephen Rothwell
2009-11-06 23:33 ` Randy Dunlap [this message]
2009-11-06 23:12   ` [PATCH -next] kmemleak: fix kconfig for crc32 build error Catalin Marinas
2009-11-06 23:35 ` [PATCH -next] staging/wireless: don't build when NET etc. are not enabled Randy Dunlap
2009-11-07 23:32   ` John W. Linville

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=4AF4B259.8030506@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=catalin.marinas@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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