From: "Manish Katiyar" <mkatiyar@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>, akpm@linux-foundation.org
Subject: Build warnings with tree in asm/boot.h & asm/setup.h
Date: Thu, 15 Jan 2009 17:40:46 +0530 [thread overview]
Message-ID: <ea11fea30901150410g5eb66065lb1918ab0b2e14cac@mail.gmail.com> (raw)
Hi,
I have a git tree synced to Linus' tree. During builds I am getting
lot build warnings like below. Perhaps someone can have a look.
Apologies if this is not the right mailing list for this.
/home/mkatiyar/personal/kernel/linux-2.6/usr/include/video/edid.h:4:
leaks CONFIG_X86 to userspace where it is not valid
/home/mkatiyar/personal/kernel/linux-2.6/usr/include/video/sisfb.h:25:
include of <linux/types.h> is preferred over <asm/types.h>
/home/mkatiyar/personal/kernel/linux-2.6/usr/include/video/sisfb.h:78:
found __[us]{8,16,32,64} type without #include <linux/types.h>
/home/mkatiyar/personal/kernel/linux-2.6/usr/include/video/uvesafb.h:5:
found __[us]{8,16,32,64} type without #include <linux/types.h>
CHECK include (0 files)
CHECK include/asm (52 files)
/home/mkatiyar/personal/kernel/linux-2.6/usr/include/asm/boot.h:14:
leaks CONFIG_PHYSICAL to userspace where it is not valid
/home/mkatiyar/personal/kernel/linux-2.6/usr/include/asm/boot.h:15:
leaks CONFIG_PHYSICAL to userspace where it is not valid
/home/mkatiyar/personal/kernel/linux-2.6/usr/include/asm/boot.h:16:
leaks CONFIG_PHYSICAL to userspace where it is not valid
/home/mkatiyar/personal/kernel/linux-2.6/usr/include/asm/boot.h:18:
leaks CONFIG_X86 to userspace where it is not valid
/home/mkatiyar/personal/kernel/linux-2.6/usr/include/asm/e820.h:13:
leaks CONFIG_NODES to userspace where it is not valid
/home/mkatiyar/personal/kernel/linux-2.6/usr/include/asm/e820.h:27:
leaks CONFIG_EFI to userspace where it is not valid
/home/mkatiyar/personal/kernel/linux-2.6/usr/include/asm/e820.h:44:
found __[us]{8,16,32,64} type without #include <linux/types.h>
/home/mkatiyar/personal/kernel/linux-2.6/usr/include/asm/kvm.h:9:
include of <linux/types.h> is preferred over <asm/types.h>
/home/mkatiyar/personal/kernel/linux-2.6/usr/include/asm/kvm.h:16:
found __[us]{8,16,32,64} type without #include <linux/types.h>
/home/mkatiyar/personal/kernel/linux-2.6/usr/include/asm/mce.h:7:
include of <linux/types.h> is preferred over <asm/types.h>
/home/mkatiyar/personal/kernel/linux-2.6/usr/include/asm/mce.h:29:
found __[us]{8,16,32,64} type without #include <linux/types.h>
/home/mkatiyar/personal/kernel/linux-2.6/usr/include/asm/mtrr.h:61:
found __[us]{8,16,32,64} type without #include <linux/types.h>
/home/mkatiyar/personal/kernel/linux-2.6/usr/include/asm/prctl.h:9:
leaks CONFIG_X86 to userspace where it is not valid
/home/mkatiyar/personal/kernel/linux-2.6/usr/include/asm/prctl.h:10:
extern's make no sense in userspace
/home/mkatiyar/personal/kernel/linux-2.6/usr/include/asm/prctl.h:11:
leaks CONFIG_X86 to userspace where it is not valid
/home/mkatiyar/personal/kernel/linux-2.6/usr/include/asm/ptrace-abi.h:83:
leaks CONFIG_X86 to userspace where it is not valid
/home/mkatiyar/personal/kernel/linux-2.6/usr/include/asm/ptrace-abi.h:86:
include of <linux/types.h> is preferred over <asm/types.h>
/home/mkatiyar/personal/kernel/linux-2.6/usr/include/asm/ptrace-abi.h:93:
found __[us]{8,16,32,64} type without #include <linux/types.h>
/home/mkatiyar/personal/kernel/linux-2.6/usr/include/asm/ptrace-abi.h:143:
leaks CONFIG_X86 to userspace where it is not valid
/home/mkatiyar/personal/kernel/linux-2.6/usr/include/asm/setup.h:15:
leaks CONFIG_X86 to userspace where it is not valid
/home/mkatiyar/personal/kernel/linux-2.6/usr/include/asm/setup.h:16:
extern's make no sense in userspace
/home/mkatiyar/personal/kernel/linux-2.6/usr/include/asm/setup.h:17:
extern's make no sense in userspace
/home/mkatiyar/personal/kernel/linux-2.6/usr/include/asm/setup.h:23:
extern's make no sense in userspace
/home/mkatiyar/personal/kernel/linux-2.6/usr/include/asm/setup.h:24:
extern's make no sense in userspace
/home/mkatiyar/personal/kernel/linux-2.6/usr/include/asm/setup.h:51:
extern's make no sense in userspace
/home/mkatiyar/personal/kernel/linux-2.6/usr/include/asm/setup.h:52:
extern's make no sense in userspace
/home/mkatiyar/personal/kernel/linux-2.6/usr/include/asm/setup.h:54:
leaks CONFIG_PARAVIRT to userspace where it is not valid
/home/mkatiyar/personal/kernel/linux-2.6/usr/include/asm/sigcontext.h:5:
include of <linux/types.h> is preferred over <asm/types.h>
/home/mkatiyar/personal/kernel/linux-2.6/usr/include/asm/sigcontext.h:24:
found __[us]{8,16,32,64} type without #include <linux/types.h>
/home/mkatiyar/personal/kernel/linux-2.6/usr/include/asm/sigcontext32.h:20:
found __[us]{8,16,32,64} type without #include <linux/types.h>
/home/mkatiyar/personal/kernel/linux-2.6/usr/include/asm/swab.h:4:
include of <linux/types.h> is preferred over <asm/types.h>
/home/mkatiyar/personal/kernel/linux-2.6/usr/include/asm/swab.h:7:
found __[us]{8,16,32,64} type without #include <linux/types.h>
/home/mkatiyar/personal/kernel/linux-2.6/usr/include/asm/swab.h:10:
leaks CONFIG_X86 to userspace where it is not valid
/home/mkatiyar/personal/kernel/linux-2.6/usr/include/asm/swab.h:40:
leaks CONFIG_X86 to userspace where it is not valid
Thanks -
Manish
reply other threads:[~2009-01-15 12:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ea11fea30901150410g5eb66065lb1918ab0b2e14cac@mail.gmail.com \
--to=mkatiyar@gmail.com \
--cc=akpm@linux-foundation.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 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®