From: Randy Dunlap <randy.dunlap@oracle.com>
To: Greg KH <greg@kroah.com>
Cc: tytso@mit.edu, Greg KH <gregkh@suse.de>,
mfasheh@suse.com, Andrew Morton <akpm@linux-foundation.org>,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
stable@kernel.org
Subject: Re: [stable] Linux 2.6.28.8 (ocfs2 build failure)
Date: Tue, 17 Mar 2009 14:02:33 -0700 [thread overview]
Message-ID: <49C00FE9.9040407@oracle.com> (raw)
In-Reply-To: <20090317205518.GA4442@kroah.com>
Greg KH wrote:
> On Tue, Mar 17, 2009 at 01:26:47PM -0700, Randy Dunlap wrote:
>> Enable all possible OCFS2 kconfig options:
>>
>>
>>
>> In file included from fs/ocfs2/alloc.c:42:
>> fs/ocfs2/journal.h: In function 'ocfs2_begin_ordered_truncate':
>> fs/ocfs2/journal.h:451: warning: passing argument 1 of 'jbd2_journal_begin_ordered_truncate' from incompatible pointer type
>> fs/ocfs2/journal.h:451: warning: passing argument 2 of 'jbd2_journal_begin_ordered_truncate' makes integer from pointer without a cast
>> fs/ocfs2/journal.h:451: error: too many arguments to function 'jbd2_journal_begin_ordered_truncate'
>> CC [M] fs/ocfs2/buffer_head_io.o
>> In file included from fs/ocfs2/aops.c:42:
>> fs/ocfs2/journal.h: In function 'ocfs2_begin_ordered_truncate':
>> fs/ocfs2/journal.h:451: warning: passing argument 1 of 'jbd2_journal_begin_ordered_truncate' from incompatible pointer type
>> fs/ocfs2/journal.h:451: warning: passing argument 2 of 'jbd2_journal_begin_ordered_truncate' makes integer from pointer without a cast
>> fs/ocfs2/journal.h:451: error: too many arguments to function 'jbd2_journal_begin_ordered_truncate'
>> make[2]: *** [fs/ocfs2/aops.o] Error 1
>> make[2]: *** Waiting for unfinished jobs....
>> In file included from fs/ocfs2/buffer_head_io.c:37:
>> fs/ocfs2/journal.h: In function 'ocfs2_begin_ordered_truncate':
>> fs/ocfs2/journal.h:451: warning: passing argument 1 of 'jbd2_journal_begin_ordered_truncate' from incompatible pointer type
>> fs/ocfs2/journal.h:451: warning: passing argument 2 of 'jbd2_journal_begin_ordered_truncate' makes integer from pointer without a cast
>> fs/ocfs2/journal.h:451: error: too many arguments to function 'jbd2_journal_begin_ordered_truncate'
>> make[2]: *** [fs/ocfs2/buffer_head_io.o] Error 1
>> make[2]: *** [fs/ocfs2/alloc.o] Error 1
>
> Did this show up in 2.6.28.7?
no.
> Odds are it's one of the jbd2 patches from Ted. Ted, any ideas?
--
~Randy
next prev parent reply other threads:[~2009-03-17 21:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 1:20 Linux 2.6.28.8 Greg KH
2009-03-17 1:20 ` Greg KH
2009-03-17 20:26 ` Linux 2.6.28.8 (ocfs2 build failure) Randy Dunlap
2009-03-17 20:55 ` [stable] " Greg KH
2009-03-17 21:02 ` Randy Dunlap [this message]
2009-03-20 22:17 ` Greg KH
2009-03-20 22:18 ` [Ocfs2-devel] " Greg KH
2009-03-23 2:44 ` Theodore Tso
2009-03-23 2:44 ` [Ocfs2-devel] " Theodore Tso
2009-03-24 0:13 ` Greg KH
2009-03-24 0:16 ` [Ocfs2-devel] " Greg KH
2009-03-24 0:13 ` Greg KH
2009-03-24 3:05 ` Theodore Tso
2009-03-24 3:05 ` [Ocfs2-devel] " Theodore Tso
2009-03-24 19:05 ` Mark Fasheh
2009-03-24 19:05 ` [Ocfs2-devel] " Mark Fasheh
2009-03-24 19:05 ` Mark Fasheh
2009-03-23 15:08 ` Linux 2.6.28.8 Martin Knoblauch
2009-03-23 23:18 ` Greg KH
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=49C00FE9.9040407@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mfasheh@suse.com \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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.