From: Pekka Enberg <penberg@cs•helsinki.fi>
To: Theodore Tso <tytso@mit•edu>,
Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Pekka Enberg <penberg@cs•helsinki.fi>,
Christoph
Subject: Re: linux-next: ext4 tree build failure
Date: Wed, 17 Jun 2009 07:16:30 +0300 [thread overview]
Message-ID: <4A386E1E.7080808@cs.helsinki.fi> (raw)
In-Reply-To: <20090616203034.GB14788@mit.edu>
Hi Ted,
Theodore Tso wrote:
> On Tue, Jun 16, 2009 at 02:44:13PM +1000, Stephen Rothwell wrote:
>> Hi Ted,
>>
>> Today's linux-next build (powerpc ppc64_defconfig) failed like this after
>> the slab tree was merged:
>>
>> In file included from fs/jbd2/checkpoint.c:26:
>> include/trace/events/jbd2.h:11: error: expected ')' before '(' token
>> include/trace/events/jbd2.h:31: error: expected ')' before '(' token
>
> Hmm... I wonder why the slab tree would be messing with tracing
> include files.
>
> Which slab tree is it? Is it Pekka's?
>
> git://git.kernel.org/pub/scm/linux/kernel/git/penberg/slab-2.6.git
Yup, that's it. I looked at this yesterday but didn't see anything
suspicious. I don't think I have any patches that mess with any tracing
include files. The only major change there should be the new default
SLQB allocator. Perhaps ext4 is simply missing some includes that are
pulled by SLUB but not SLQB?
Pekka
next prev parent reply other threads:[~2009-06-17 4:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 4:44 linux-next: ext4 tree build failure Stephen Rothwell
2009-06-16 20:30 ` Theodore Tso
2009-06-16 22:11 ` Theodore Tso
2009-06-17 5:46 ` Stephen Rothwell
2009-06-17 4:16 ` Pekka Enberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-12-10 0:38 Stephen Rothwell
2009-12-10 2:10 ` tytso
2009-12-10 2:33 ` Stephen Rothwell
2009-04-28 1:27 Stephen Rothwell
2009-04-28 11:23 ` Theodore Tso
2009-04-28 11:44 ` 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=4A386E1E.7080808@cs.helsinki.fi \
--to=penberg@cs$(echo .)helsinki.fi \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=tytso@mit$(echo .)edu \
/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