From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: linux-next: kmemleak tree build failure
Date: Thu, 30 Jul 2009 16:00:12 +1000 [thread overview]
Message-ID: <20090730160012.5814e251.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 633 bytes --]
Hi Catalin,
Today's linux-next build (x86_64 allmodconfig) failed like this:
arch/x86/kernel/process.c: In function 'free_thread_info':
arch/x86/kernel/process.c:58: error: implicit declaration of function 'kmemleak_free'
Caused by commit 3d898087320a732ec853c98f244253892616840f ("kmemleak:
Inform kmemleak about kernel stack allocation") from the kmemleak tree.
Probably a missing include of linux/kmemleak.h.
I have dropped the kmemleak tree for today. (It accidentally did not
get included yesterday.)
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2009-07-30 6:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 6:00 Stephen Rothwell [this message]
2009-07-30 8:58 ` linux-next: kmemleak tree build failure Catalin Marinas
2009-07-31 2:00 ` Stephen Rothwell
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=20090730160012.5814e251.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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