From: Ingo Molnar <mingo@elte.hu>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Jaswinder Singh Rajput <jaswinder@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
David Miller <davem@davemloft.net>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kbuild: drop check for CONFIG_ in headers_check
Date: Sat, 31 Jan 2009 01:41:11 +0100 [thread overview]
Message-ID: <20090131004111.GB13709@elte.hu> (raw)
In-Reply-To: <200901310127.03142.arnd@arndb.de>
* Arnd Bergmann <arnd@arndb.de> wrote:
> On Saturday 31 January 2009, Ingo Molnar wrote:
> > Jaswinder, i think we now have a realistic chance to reach a zero baseline
> > with these warnings, for v2.6.29. Here are the remaining warnings (summed
> > up per file) on x86 (after Sam's patch):
> >
> > 17 /dev/shm/tip/usr/include/linux/reiserfs_fs.h
> > 12 /dev/shm/tip/usr/include/linux/soundcard.h
> > 3 /dev/shm/tip/usr/include/linux/nubus.h
> > 2 /dev/shm/tip/usr/include/linux/in6.h
> > 1 /dev/shm/tip/usr/include/mtd/jffs2-user.h
> > 1 /dev/shm/tip/usr/include/linux/socket.h
> > 1 /dev/shm/tip/usr/include/linux/coda_psdev.h
> > 1 /dev/shm/tip/usr/include/linux/bsg.h
> >
>
> Ah, that doesn't look too bad. On a related subject, was there ever a
> conclusion about whether we want to support __KERNEL_STRICT_NAMES in
> every header? When that is set, headers cannot use most of the standard
> types (dev_t, mode_t, off_t, pid_t, suseconds_t, timer_t, uid_t, gid_t,
> loff_t, time_t, clock_t, caddr_t, pgoff_t, {u_,u,}int{8,16,32,64}_6})
> but have to use the __kernel_* versions of that.
hm, that looks quite ugly and unnatural. Could the usr/* exporting scripts
convert these types automatically to the __kernel_* versions?
Ingo
next prev parent reply other threads:[~2009-01-31 0:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 19:04 [git pull V2] headers_check fixes Jaswinder Singh Rajput
2009-01-30 19:26 ` Ingo Molnar
2009-01-30 20:40 ` Arnd Bergmann
2009-01-30 22:56 ` [PATCH] kbuild: drop check for CONFIG_ in headers_check Sam Ravnborg
2009-01-30 23:40 ` Ingo Molnar
2009-01-31 0:27 ` Arnd Bergmann
2009-01-31 0:41 ` Ingo Molnar [this message]
2009-01-31 1:06 ` Arnd Bergmann
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=20090131004111.GB13709@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=torvalds@linux-foundation.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