From: Jaswinder Singh Rajput <jaswinderlinux@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Harvey Harrison <harvey.harrison@gmail.com>,
Sam Ravnborg <sam@ravnborg.org>,
LKML <linux-kernel@vger.kernel.org>,
Cyrill Gorcunov <gorcunov@gmail.com>,
Jaswinder Singh Rajput <jaswinderrajput@gmail.com>
Subject: Re: Can we get warnings from the x86 userspace headers fixed?
Date: Tue, 13 Jan 2009 12:33:59 +0530 [thread overview]
Message-ID: <3f9a31f40901122303m4e37c33ag5b308eb538d4e60b@mail.gmail.com> (raw)
In-Reply-To: <20090112213719.GC7320@elte.hu>
On Tue, Jan 13, 2009 at 3:07 AM, Ingo Molnar <mingo@elte.hu> wrote:
>
> * Harvey Harrison <harvey.harrison@gmail.com> wrote:
>
>> On Mon, 2009-01-12 at 22:28 +0100, Sam Ravnborg wrote:
>> > 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...
>> >
>>
>> I'll have a go at some of them this afternoon unless someone beats me to
>> it.
>
> thanks Harvey! Please work against tip/master if you do that, there's a
> few header file changes in the queue already.
>
Some patches are also available in:
http://git.kernel.org/?p=linux/kernel/git/jaswinder/linux-2.6-tiptop.git;a=summary
Thanks
--
JSR
next prev parent reply other threads:[~2009-01-13 7:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 21:28 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 [this message]
2009-01-12 22:14 ` Cyrill Gorcunov
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=3f9a31f40901122303m4e37c33ag5b308eb538d4e60b@mail.gmail.com \
--to=jaswinderlinux@gmail.com \
--cc=gorcunov@gmail.com \
--cc=harvey.harrison@gmail.com \
--cc=jaswinderrajput@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
Powered by JetHome