From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Mark Fasheh <mfasheh@suse•com>
Cc: linux-next@vger•kernel.org, Sunil Mushran <sunil.mushran@oracle•com>
Subject: linux-next: ocfs2 tree build failure
Date: Thu, 8 Jan 2009 13:01:58 +1100 [thread overview]
Message-ID: <20090108130158.d222ceea.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 885 bytes --]
Hi Mark,
Today's linux-next build (x86_64 allmodconfig) failed like this:
fs/ocfs2/super.c: In function 'ocfs2_osb_dump':
fs/ocfs2/super.c:256: error: dereferencing pointer to incomplete type
fs/ocfs2/super.c:256: error: dereferencing pointer to incomplete type
fs/ocfs2/super.c:256: error: dereferencing pointer to incomplete type
fs/ocfs2/super.c:259: error: dereferencing pointer to incomplete type
fs/ocfs2/super.c:261: error: dereferencing pointer to incomplete type
Caused by commit 796868c27387ba9bbad6b9c6b770ed34e2809a73 ("ocfs2: Expose
the file system state via debugfs") since (despite being declared in
fs/ocfs2/ocfs2.h) the struct ocfs2_recovery_map definition is not exposed
beyond fs/ocfs2/journal.c.
I have dropped the ocfs2 tree for today.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2009-01-08 2:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 2:01 Stephen Rothwell [this message]
2009-01-08 2:14 ` linux-next: ocfs2 tree build failure Sunil Mushran
2009-01-09 2:05 ` Mark Fasheh
-- strict thread matches above, loose matches on Subject: below --
2008-11-25 5:42 Stephen Rothwell
2008-11-26 5:30 ` Stephen Rothwell
2008-11-26 20:43 ` Mark Fasheh
2008-11-26 23:42 ` Stephen Rothwell
2008-11-26 23:49 ` Mark Fasheh
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=20090108130158.d222ceea.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mfasheh@suse$(echo .)com \
--cc=sunil.mushran@oracle$(echo .)com \
/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