From: <mail@viliar.net.ru>
To: Reiserfs mail-list <Reiserfs-List@namesys.com>
Subject: 2.6.16+reiser4+openvz patches = error.
Date: Tue, 11 Jul 2006 22:18:21 +0400 [thread overview]
Message-ID: <web-9729233@inc.ru> (raw)
Hello All!
I'm trying to compile 2.6.16 kernel with this openvz patch:
(http://download.openvz.org/kernel/devel/026test015.1/patches/patch-026test015-combined.gz)
(changes: http://openvz.org/news/updates/devel-kernel-026test015.1)
and with reiser4-for-2.6.16-4.patch.gz.
Patching is finished without errors, but in process of compilation (reiser4 - module) I get those
errors:
CC [M] fs/reiser4/plugin/object.o
fs/reiser4/plugin/object.c:96: warning: initialization from incompatible pointer type
fs/reiser4/plugin/object.c:208: warning: initialization from incompatible pointer type
fs/reiser4/plugin/object.c:254: warning: initialization from incompatible pointer type
fs/reiser4/plugin/object.c:300: warning: initialization from incompatible pointer type
fs/reiser4/plugin/object.c:392: warning: initialization from incompatible pointer type
fs/reiser4/plugin/object.c:452: warning: initialization from incompatible pointer type
CC [M] fs/reiser4/plugin/cluster.o
CC [M] fs/reiser4/plugin/inode_ops.o
fs/reiser4/plugin/inode_ops.c: In function 'permission_common':
fs/reiser4/plugin/inode_ops.c:416: error: too few arguments to function 'generic_permission'
make[2]: *** [fs/reiser4/plugin/inode_ops.o] Error 1
make[1]: *** [fs/reiser4] Error 2
make: *** [fs] Error 2
Is where any ideas, why it could be?
Thank you.
A.
-------------
"Hic Jacet Ego"
next reply other threads:[~2006-07-11 18:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-11 18:18 mail [this message]
2006-07-12 13:38 ` 2.6.16+reiser4+openvz patches = error Brian Uhrain
2006-07-12 13:49 ` mail
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=web-9729233@inc.ru \
--to=mail@viliar.net.ru \
--cc=Reiserfs-List@namesys.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.