From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: 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>,
Catalin Marinas <catalin.marinas@arm.com>,
npiggin@suse.de
Subject: Re: linux-next: slab tree build failure
Date: Mon, 07 Sep 2009 10:43:46 +0300 [thread overview]
Message-ID: <1252309426.4964.3.camel@penberg-laptop> (raw)
In-Reply-To: <20090907173108.3c0148d7.sfr@canb.auug.org.au>
Hi Stephen,
On Mon, 7 Sep 2009 09:10:18 +0300 Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> > AFAICT, you're interested in kmemleak.git, not slab.git. Catalin?
On Mon, 2009-09-07 at 17:31 +1000, Stephen Rothwell wrote:
> I first got the error after merging the slab tree ... the kmemleak tree
> is merged much later.
Aah, let me guess, CONFIG_SLQB? I guess I'll just rebase the damn tree
and make it non-default. We need that anyway if we want to merge it to
2.6.32. I'll take a stab at it later this evening (my time zone).
Pekka
next prev parent reply other threads:[~2009-09-07 7:43 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 [this message]
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
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=1252309426.4964.3.camel@penberg-laptop \
--to=penberg@cs.helsinki.fi \
--cc=catalin.marinas@arm.com \
--cc=cl@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.com \
--cc=npiggin@suse.de \
--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