From: Pekka Enberg <penberg@kernel.org>
To: Christoph Lameter <cl@linux.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the slab tree
Date: Thu, 11 Jul 2013 09:42:35 +0300 [thread overview]
Message-ID: <51DE53DB.1010104@kernel.org> (raw)
In-Reply-To: <0000013fc9e9f94b-e87067d6-0bb6-41b3-ae83-ed8f110f893f-000000@email.amazonses.com>
On Wed, 10 Jul 2013, Pekka Enberg wrote:
>> Yes, it indeed interacts badly with kmemleak and tracing. I reverted the
>> commit.
On 07/10/2013 09:48 PM, Christoph Lameter wrote:
> Here is the fix required. kmemleak.h is weird in that it cannot be
> included at the top of slab.h due to its corresponding dependency on
> slab.h. Bad situation. kmemleak.h itself should include "slab.h"...
Can you please resend these after the merge window closes?
Pekka
next prev parent reply other threads:[~2013-07-11 6:42 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 2:56 linux-next: build failure after merge of the slab tree Stephen Rothwell
2013-07-10 7:00 ` Pekka Enberg
2013-07-10 18:48 ` Christoph Lameter
2013-07-11 6:42 ` Pekka Enberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-01 5:28 Stephen Rothwell
2024-05-01 15:31 ` Vlastimil Babka
2022-11-25 1:49 Stephen Rothwell
2022-11-25 7:50 ` Vlastimil Babka
2022-11-24 4:39 Stephen Rothwell
2022-11-24 8:56 ` Vlastimil Babka
2022-09-06 6:51 Stephen Rothwell
2022-09-06 7:53 ` Vlastimil Babka
2022-09-06 18:37 ` Alexei Starovoitov
2022-09-07 3:05 ` Alexei Starovoitov
2022-09-07 6:40 ` Vlastimil Babka
2022-09-07 7:45 ` Stephen Rothwell
2011-01-31 3:42 Stephen Rothwell
2011-01-31 19:32 ` Pekka Enberg
2011-02-03 15:19 ` Christoph Lameter
2011-02-08 15:53 ` Christoph Lameter
2011-02-08 15:55 ` Christoph Lameter
2011-02-08 16:50 ` Ted Ts'o
2011-02-08 17:11 ` Sedat Dilek
2011-02-08 17:11 ` Sedat Dilek
2011-02-08 17:44 ` Christoph Lameter
2010-12-09 3:03 Stephen Rothwell
2010-12-09 16:25 ` Pekka Enberg
2010-10-27 0:33 Stephen Rothwell
2010-10-27 7:29 ` 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=51DE53DB.1010104@kernel.org \
--to=penberg@kernel.org \
--cc=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.