From: nyk <nyk@giantx.co.uk>
To: linux-kernel@vger.kernel.org
Subject: 2.6.14-rc4-mm1 ntfs/namei.c missing compat.h?
Date: Mon, 17 Oct 2005 15:49:00 +0100 [thread overview]
Message-ID: <20051017144900.GA2942@giantx.co.uk> (raw)
Hi,
Looks like fs/ntfs/namei.c is missing linux/compat.h
CHK include/linux/version.h
CHK include/linux/compile.h
CHK usr/initramfs_list
CC [M] fs/ntfs/namei.o
In file included from include/linux/dcache.h:6,
from fs/ntfs/namei.c:23:
include/asm/atomic.h:383: error: syntax error before '*' token
include/asm/atomic.h:384: warning: function declaration isn't a prototype
include/asm/atomic.h: In function 'atomic_scrub':
include/asm/atomic.h:385: error: 'u32' undeclared (first use in this function)
include/asm/atomic.h:385: error: (Each undeclared identifier is reported only once
include/asm/atomic.h:385: error: for each function it appears in.)
include/asm/atomic.h:385: error: syntax error before 'i'
include/asm/atomic.h:386: error: 'i' undeclared (first use in this function)
include/asm/atomic.h:386: error: 'size' undeclared (first use in this function)
include/asm/atomic.h:386: error: 'virt_addr' undeclared (first use in this function)
include/asm/atomic.h:386: warning: left-hand operand of comma expression has no effect
include/asm/atomic.h:386: warning: statement with no effect
include/asm/atomic.h:390: error: memory input 0 is not directly addressable
make[2]: *** [fs/ntfs/namei.o] Error 1
make[1]: *** [fs/ntfs] Error 2
make: *** [fs] Error 2
Compiles fine with #include <linux/compat.h> added to the top of
fs/ntfs/namei.c
If that's the right place for it, of course.
hth
Nyk
--
/__
\_|\/
/\
next reply other threads:[~2005-10-17 14:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-17 14:49 nyk [this message]
2005-10-17 15:09 ` Anton Altaparmakov
2005-10-17 16:33 ` [patch] " Tim Schmielau
2005-10-17 16:41 ` Andi Kleen
2005-10-17 18:01 ` Alan Cox
2005-10-17 18:02 ` Andi Kleen
2005-10-17 19:39 ` nyk
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=20051017144900.GA2942@giantx.co.uk \
--to=nyk@giantx.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®