From: Catalin Marinas <catalin.marinas@arm•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: kmemleak tree build failure
Date: Thu, 30 Jul 2009 09:58:57 +0100 [thread overview]
Message-ID: <1248944337.3376.5.camel@pc1117.cambridge.arm.com> (raw)
In-Reply-To: <20090730160012.5814e251.sfr@canb.auug.org.au>
On Thu, 2009-07-30 at 16:00 +1000, Stephen Rothwell wrote:
> 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.
Yes, it's missing this (I was only testing it with slub which has
kmemleak.h included in its header file).
I updated the kmemleak branch now. Thanks.
--
Catalin
next prev parent reply other threads:[~2009-07-30 8:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 6:00 linux-next: kmemleak tree build failure Stephen Rothwell
2009-07-30 8:58 ` Catalin Marinas [this message]
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=1248944337.3376.5.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=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