From: Catalin Marinas <catalin.marinas@arm•com>
To: Randy Dunlap <randy.dunlap@oracle•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>
Subject: Re: [PATCH -next] kmemleak: fix kconfig for crc32 build error
Date: Fri, 06 Nov 2009 23:12:30 +0000 [thread overview]
Message-ID: <1257549150.19025.2.camel@pc1117.cambridge.arm.com> (raw)
In-Reply-To: <4AF4B259.8030506@oracle.com>
On Fri, 2009-11-06 at 15:33 -0800, Randy Dunlap wrote:
> 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'
Thanks for the patch. I'll included it in my kmemleak branch.
--
Catalin
next prev parent reply other threads:[~2009-11-06 23:12 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 ` [PATCH -next] kmemleak: fix kconfig for crc32 build error Randy Dunlap
2009-11-06 23:12 ` Catalin Marinas [this message]
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=1257549150.19025.2.camel@pc1117.cambridge.arm.com \
--to=catalin.marinas@arm$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=randy.dunlap@oracle$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/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