From: "H. Peter Anvin" <hpa@zytor.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Jaswinder Singh Rajput <jaswinder@kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
mingo@elte.hu, x86@kernel.org, sam@ravnborg.org,
jirislaby@gmail.com, gregkh@suse.de, davem@davemloft.net,
xyzzy@speakeasy.org, mchehab@infradead.org,
jens.axboe@oracle.com, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org, Avi Kivity <avi@redhat.com>
Subject: Re: [GIT PULL -tip] fix 22 make headers_check - 200901
Date: Wed, 04 Feb 2009 09:33:51 -0800 [thread overview]
Message-ID: <4989D17F.4030406@zytor.com> (raw)
In-Reply-To: <200902041255.53264.arnd@arndb.de>
Arnd Bergmann wrote:
>
> I fear that the problem might be more widespread than just kvm.
> The problem is that <linux/types.h> without __KERNEL_STRICT_NAMES
> defines the standard types that glibc provides in its own <sys/types.h>,
> some of them even defined differently (e.g. the size of off_t depends
> __USE_FILE_OFFSET64).
>
> Subject: introduce <linux/strict_types.h>
>
Actually, if anything we should move the *non* __KERNEL_STRICT_NAMES out
of <linux/types.h> into something else, or completely deep-six them. I
don't know of any libc which wants these anymore, and I think they're
just residual libc5 cruft.
However, if we want <linux/extra_types.h> that's fine with me; but
<linux/types.h> really should be clean, which means doing what
__KERNEL_STRICT_NAMES does now.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2009-02-04 17:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-24 12:56 [GIT PULL -tip] fix 22 make headers_check - 200901 Jaswinder Singh Rajput
2009-01-24 13:43 ` Jaswinder Singh Rajput
2009-01-26 12:50 ` Ingo Molnar
2009-02-04 6:43 ` Herbert Xu
2009-02-04 8:04 ` Jaswinder Singh Rajput
2009-02-04 8:12 ` Avi Kivity
2009-02-04 8:13 ` Avi Kivity
2009-02-04 8:37 ` Jaswinder Singh Rajput
2009-02-04 11:55 ` Arnd Bergmann
2009-02-04 14:18 ` Ingo Molnar
2009-02-04 17:33 ` H. Peter Anvin [this message]
2009-02-05 14:30 ` Arnd Bergmann
2009-02-05 14:30 ` Arnd Bergmann
2009-02-05 15:17 ` H. Peter Anvin
2009-02-05 16:07 ` [PATCH] Make exported headers use strict posix types Arnd Bergmann
2009-02-05 17:54 ` H. Peter Anvin
2009-02-05 18:45 ` Arnd Bergmann
2009-02-05 18:45 ` Arnd Bergmann
2009-02-17 9:38 ` Mauro Carvalho Chehab
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=4989D17F.4030406@zytor.com \
--to=hpa@zytor.com \
--cc=arnd@arndb.de \
--cc=avi@redhat.com \
--cc=davem@davemloft.net \
--cc=gregkh@suse.de \
--cc=herbert@gondor.apana.org.au \
--cc=jaswinder@kernel.org \
--cc=jens.axboe@oracle.com \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.org \
--cc=x86@kernel.org \
--cc=xyzzy@speakeasy.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.