From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Can we get warnings from the x86 userspace headers fixed?
Date: Tue, 13 Jan 2009 01:14:12 +0300 [thread overview]
Message-ID: <20090112221412.GG13384@localhost> (raw)
In-Reply-To: <20090112212855.GB15185@uranus.ravnborg.org>
[Sam Ravnborg - Mon, Jan 12, 2009 at 10:28:55PM +0100]
| Hi Ingo.
|
| We have recently introduced a lot of new warnings for our
| userspace headers.
|
| Try to do a "make headers_check" and enjoy...
|
| Are there any chance you could ask one of your helpers to
| start to look into the x86 specific ones?
|
| If we get x86 clean this would create more incentive to
| make the generic clean too.
|
| I had originally planned to attack the generic headers
| (include/linux/*) but I'm faced by reality after my
| vacation and has almost no spare time for the time being.
|
| I already fixed the sparc headers but that is not
| visible compared to x86 (the fixes was btw easy).
|
| I can try to help by doing a few reviews in the
| beginning but I need to fix kbuild stuff first where
| I have a few serious issues pending. And lacks time...
|
| Sam
|
Sam, I hope to find some spare time for this
tomorrow (it's night here). At least in one
moment headers_check assume that CONFIG is exported
into user space even being bound by pure C comments.
---
/home/cyrill/projects/kernel/linux-2.6.git/usr/include/asm/e820.h:13: leaks
CONFIG_NODES to userspace where it is not valid
---
Just a note.
- Cyrill -
prev parent reply other threads:[~2009-01-12 22:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 21:28 Can we get warnings from the x86 userspace headers fixed? Sam Ravnborg
2009-01-12 21:31 ` Harvey Harrison
2009-01-12 21:36 ` Sam Ravnborg
2009-01-12 21:37 ` Ingo Molnar
2009-01-12 21:44 ` Cyrill Gorcunov
2009-01-12 21:48 ` Cyrill Gorcunov
2009-01-13 7:03 ` Jaswinder Singh Rajput
2009-01-12 22:14 ` Cyrill Gorcunov [this message]
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=20090112221412.GG13384@localhost \
--to=gorcunov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.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