From: Arkadiusz Miskiewicz <arekm@pld-linux.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.27.32
Date: Wed, 09 Sep 2009 09:10:50 +0200 [thread overview]
Message-ID: <h87kdq$us2$1@ger.gmane.org> (raw)
In-Reply-To: 20090909040829.GA9657@kroah.com
Greg KH wrote:
> I'm announcing the release of the 2.6.27.32 kernel. All users of the
> 2.6.27 kernel series are very strongly encouraged to upgrade.
CC [M] fs/ocfs2/aops.o
fs/ocfs2/aops.c: In function 'ocfs2_write_cluster':
fs/ocfs2/aops.c:1286: error: 'should_zero' undeclared (first use in this
function)
fs/ocfs2/aops.c:1286: error: (Each undeclared identifier is reported only
once
fs/ocfs2/aops.c:1286: error: for each function it appears in.)
fs/ocfs2/aops.c: In function 'ocfs2_write_cluster_by_desc':
fs/ocfs2/aops.c:1360: warning: passing argument 4 of 'ocfs2_write_cluster'
makes pointer from integer without a cast
fs/ocfs2/aops.c:1235: note: expected 'struct ocfs2_alloc_context *' but
argument is of type 'unsigned int'
fs/ocfs2/aops.c:1360: warning: passing argument 6 of 'ocfs2_write_cluster'
from incompatible pointer type
fs/ocfs2/aops.c:1235: note: expected 'struct ocfs2_write_ctxt *' but
argument is of type 'struct ocfs2_alloc_context *'
fs/ocfs2/aops.c:1360: warning: passing argument 7 of 'ocfs2_write_cluster'
makes integer from pointer without a cast
fs/ocfs2/aops.c:1235: note: expected 'u32' but argument is of type 'struct
ocfs2_write_ctxt *'
fs/ocfs2/aops.c:1360: error: too many arguments to function
'ocfs2_write_cluster'
make[2]: *** [fs/ocfs2/aops.o] Error 1
--
Arkadiusz Miśkiewicz PLD/Linux Team
arekm / maven.pl http://ftp.pld-linux.org/
next prev parent reply other threads:[~2009-09-09 7:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 4:08 Linux 2.6.27.32 Greg KH
2009-09-09 4:08 ` Greg KH
2009-09-09 7:10 ` Arkadiusz Miskiewicz [this message]
2009-09-09 13:28 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2009-09-09 14:40 Jayson King
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='h87kdq$us2$1@ger.gmane.org' \
--to=arekm@pld-linux.org \
--cc=linux-kernel@vger.kernel.org \
/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.