From: Catalin Marinas <catalin.marinas@arm•com>
To: Pekka Enberg <penberg@cs•helsinki.fi>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Christoph Lameter <cl@linux-foundation•org>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
"Luis R. Rodriguez" <lrodriguez@atheros•com>,
"John W. Linville" <linville@tuxdriver•com>
Subject: Re: linux-next: slab tree build failure
Date: Mon, 07 Sep 2009 09:35:09 +0100 [thread overview]
Message-ID: <1252312509.23780.15.camel@pc1117.cambridge.arm.com> (raw)
In-Reply-To: <84144f020909062310u37ecdddfw31c6cc9a22ccabd9@mail.gmail.com>
On Mon, 2009-09-07 at 09:10 +0300, Pekka Enberg wrote:
> Hi Stephen,
>
> On Mon, Sep 7, 2009 at 8:37 AM, Stephen Rothwell<sfr@canb•auug.org.au> wrote:
> > Hi all,
> >
> > Today's linux-next build (x86_64 allmodconfig) failed like this:
> >
> > net/wireless/scan.c: In function 'cfg80211_inform_bss':
> > net/wireless/scan.c:499: error: implicit declaration of function 'kmemleak_ignore'
> >
> > Caused by commit 74ce35c0d2261896ed4d49799311a894520f7a94 ("cfg80211:
> > clear cfg80211_inform_bss() from kmemleak reports") from the wireless
> > tree (which should have included linux/kmemleak.h into
> > net/wireless/scan.c). Some interaction with the slab tree has exposed
> > this.
> >
> > I have reverted the above commit for today.
>
> AFAICT, you're interested in kmemleak.git, not slab.git. Catalin?
I think that's a commit from Luis. It shouldn't have been merged in the
first instance anyway (we shouldn't randomly ignore kmemleak reports
unless we know for sure why kmemleak thinks it is a leak and we should
write a comment explaining why).
--
Catalin
next prev parent reply other threads:[~2009-09-07 8:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-07 5:37 linux-next: slab tree build failure Stephen Rothwell
2009-09-07 6:10 ` Pekka Enberg
2009-09-07 7:31 ` Stephen Rothwell
2009-09-07 7:43 ` Pekka Enberg
2009-09-07 8:29 ` Stephen Rothwell
2009-09-07 9:04 ` Heiko Carstens
2009-09-07 9:22 ` Pekka Enberg
2009-09-07 8:35 ` Catalin Marinas [this message]
2009-09-08 16:32 ` Luis R. Rodriguez
-- strict thread matches above, loose matches on Subject: below --
2009-12-08 3:44 Stephen Rothwell
2009-12-07 4:11 Stephen Rothwell
2009-06-19 4:16 Stephen Rothwell
2009-06-19 10:40 ` Benjamin Herrenschmidt
2009-06-22 9:09 ` Pekka Enberg
2008-11-03 4:42 Stephen Rothwell
2008-11-03 5:14 ` Dave Chinner
2008-11-03 9:38 ` Pekka Enberg
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=1252312509.23780.15.camel@pc1117.cambridge.arm.com \
--to=catalin.marinas@arm$(echo .)com \
--cc=cl@linux-foundation$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linville@tuxdriver$(echo .)com \
--cc=lrodriguez@atheros$(echo .)com \
--cc=penberg@cs$(echo .)helsinki.fi \
--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