From: Dave Chinner <david@fromorbit.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: xfs-masters@oss.sgi.com, linux-next@vger.kernel.org
Subject: Re: linux-next: xfs tree build failure
Date: Thu, 12 Mar 2009 09:52:12 +1100 [thread overview]
Message-ID: <20090311225212.GN26138@disturbed> (raw)
In-Reply-To: <20090310134547.e5d1d9ee.sfr@canb.auug.org.au>
On Tue, Mar 10, 2009 at 01:45:47PM +1100, Stephen Rothwell wrote:
> Hi David,
>
> Today's linux-next build (x86_64 allmodconfig) failed like this:
>
> In file included from fs/xfs/support/debug.c:21:
> fs/xfs/xfs_error.h:137: error: expected declaration specifiers or '...' before 'xfs_mount_t'
> fs/xfs/xfs_error.h:138: error: expected ')' before '*' token
>
> Immediate cause is commit 7bf446f8b581cef434f5ff05e8a791563bc09b7f ("xfs:
> include header files for prototypes").
Obviously nobody built this on a CONFIG_XFS_DEBUG=y kernel before
pushing it. Moving the xfs_error.h include down below all the other
includes (i.e after xfs_mount.h) will fix the problem....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2009-03-11 22:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 2:45 linux-next: xfs tree build failure Stephen Rothwell
2009-03-11 22:52 ` Dave Chinner [this message]
2009-03-12 1:04 ` Stephen Rothwell
2009-03-15 12:18 ` Dave Chinner
2009-03-15 13:33 ` [xfs-masters] " Felix Blyakher
2009-03-15 14:07 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2009-09-02 1:25 Stephen Rothwell
2009-09-02 1:28 ` Christoph Hellwig
2009-09-02 1:54 ` Felix Blyakher
2009-09-02 2:00 ` Stephen Rothwell
2009-07-03 0:05 Stephen Rothwell
2008-12-03 23:16 Stephen Rothwell
2008-12-04 5:20 ` Eric Sandeen
2008-10-30 2:23 Stephen Rothwell
2008-10-30 9:08 ` Dave Chinner
2008-11-05 2:20 ` Stephen Rothwell
2008-11-05 20:47 ` Dave Chinner
2008-11-06 15:27 ` Christoph Hellwig
2008-11-07 5:06 ` Stephen Rothwell
2008-11-11 2:05 ` Lachlan McIlroy
2008-11-11 2:11 ` 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=20090311225212.GN26138@disturbed \
--to=david@fromorbit.com \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=xfs-masters@oss.sgi.com \
/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.