From: Jaswinder Singh Rajput <jaswinderlinux@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Jaswinder Singh Rajput <jaswinder@infradead.org>,
Ingo Molnar <mingo@elte.hu>, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
David Miller <davem@davemloft.net>,
x86 maintainers <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>
Subject: Re: [PULL -tip] fixed few make headers_check warnings
Date: Wed, 14 Jan 2009 14:59:54 +0530 [thread overview]
Message-ID: <3f9a31f40901140129i1389f47frf32808f3a695a118@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0901140954250.27308@anakin>
Hello Geert,
On Wed, Jan 14, 2009 at 2:26 PM, Geert Uytterhoeven
<geert@linux-m68k.org> wrote:
> On Tue, 13 Jan 2009, Jaswinder Singh Rajput wrote:
>> Please pull these patches. Earlier I also floated these patches so that I can get some feedback.
>>
>> The following changes since commit ae2659bcd0b5bf34dd4b03f1db0a2942cc09b8e6:
>> Ingo Molnar (1):
>> Merge branch 'x86/mm'
>>
>> are available in the git repository at:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/jaswinder/linux-2.6-tiptop.git master
>>
>> Jaswinder Singh Rajput (7):
>> include of <linux/types.h> is preferred over <asm/types.h>
>> found __[us]{8,16,32,64} type without #include <linux/types.h>
>> capability.h: extern's make no sense in userspace
>> coda_psdev.h: extern's make no sense in userspace
>> in6.h: extern's make no sense in userspace
>> nubus.h: extern's make no sense in userspace
>> socket.h: extern's make no sense in userspace
>
> May I please remind you of my comment in
> http://patchwork.kernel.org/patch/2093/?
>
Thanks for your reminder :-)
> At least nubus.h still leaks forward declarations for kernel functions that
> lack the "extern" keyword, so they still pollute user space.
>
Yes, you are right, I just tried to pampered weeping warning messages
which is annoying.
In this subset, I just try to fix 77 such warnings.
nubus.h still have such warnings and other fixes required which you
are pointing so I am expecting nubus people will solve such problems.
Thanks
--
JSR
next prev parent reply other threads:[~2009-01-14 9:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 8:40 [PULL -tip] fixed few make headers_check warnings Jaswinder Singh Rajput
2009-01-13 12:49 ` Ingo Molnar
2009-01-13 21:03 ` David Miller
2009-01-14 15:40 ` Sam Ravnborg
2009-01-14 15:58 ` Oliver Hartkopp
2009-01-15 10:54 ` Ingo Molnar
2009-01-14 8:56 ` Geert Uytterhoeven
2009-01-14 9:29 ` Jaswinder Singh Rajput [this message]
2009-01-14 15:38 ` Sam Ravnborg
2009-01-14 15:59 ` Jaswinder Singh Rajput
2009-01-14 16:36 ` Geert Uytterhoeven
2009-01-14 16:58 ` Jaswinder Singh Rajput
2009-01-14 20:15 ` Sam Ravnborg
2009-01-15 11:11 ` Ingo Molnar
2009-01-15 14:37 ` Sam Ravnborg
2009-01-15 14:47 ` Jaswinder Singh Rajput
2009-01-15 14:50 ` Ingo Molnar
2009-01-15 14:51 ` Ingo Molnar
2009-01-15 15:16 ` Jaswinder Singh Rajput
2009-01-15 15:33 ` Ingo Molnar
2009-01-15 14:49 ` Ingo Molnar
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=3f9a31f40901140129i1389f47frf32808f3a695a118@mail.gmail.com \
--to=jaswinderlinux@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=jaswinder@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).