From: Sunil Mushran <sunil.mushran@oracle.com>
To: Mark Fasheh <mfasheh@suse.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Subject: Re: linux-next: ocfs2 tree build failure
Date: Wed, 07 Jan 2009 18:14:45 -0800 [thread overview]
Message-ID: <49656195.2070001@oracle.com> (raw)
In-Reply-To: <20090108130158.d222ceea.sfr@canb.auug.org.au>
http://oss.oracle.com/pipermail/ocfs2-devel/2008-December/003552.html
This needs to be added.
Stephen Rothwell wrote:
> 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.
>
next prev parent reply other threads:[~2009-01-08 2:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 2:01 linux-next: ocfs2 tree build failure Stephen Rothwell
2009-01-08 2:14 ` Sunil Mushran [this message]
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=49656195.2070001@oracle.com \
--to=sunil.mushran@oracle.com \
--cc=linux-next@vger.kernel.org \
--cc=mfasheh@suse.com \
--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.