linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "H.J. Lu" <hjl.tools@gmail.com>,
	linux-arch@vger.kernel.org, Vineet.Gupta1@synopsys.com,
	linux-kernel@vger.kernel.org,
	James Hogan <james.hogan@imgtec.com>
Subject: Re: new architectures, time_t __kernel_long_t
Date: Thu, 15 Nov 2012 07:10:12 -0800	[thread overview]
Message-ID: <50A505D4.1080606@zytor.com> (raw)
In-Reply-To: <201211151436.23088.arnd@arndb.de>

On 11/15/2012 06:36 AM, Arnd Bergmann wrote:
>>
>> Glibc has been providing its own types for years.
>> Kernel provided types used to be wrong for ia32
>> on x86-64.
>
> What about ioctls and other calls then that actually do rely on the
> kernel headers and use the __kernel_*_t types?
>

Now, glibc *shouldn't* have to do that... it is an indication of failure 
on our part.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

  parent reply	other threads:[~2012-11-15 15:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-14 12:18 new architectures, time_t __kernel_long_t Arnd Bergmann
2012-11-14 12:48 ` Geert Uytterhoeven
2012-11-14 16:26 ` H. Peter Anvin
2012-11-14 16:26   ` H. Peter Anvin
2012-11-15  9:14   ` Arnd Bergmann
2012-11-15  9:14     ` Arnd Bergmann
2012-11-15 13:59     ` H.J. Lu
2012-11-15 14:36       ` Arnd Bergmann
2012-11-15 14:42         ` H.J. Lu
2012-11-15 15:10         ` H. Peter Anvin [this message]
2012-12-21  4:57 ` Al Viro
2012-12-21  5:00   ` H. Peter Anvin
2012-12-21  5:02     ` Al Viro
2012-12-21  5:05       ` H. Peter Anvin
2012-12-21  5:19         ` Al Viro
2012-12-21  5:47           ` H. Peter Anvin

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=50A505D4.1080606@zytor.com \
    --to=hpa@zytor.com \
    --cc=Vineet.Gupta1@synopsys.com \
    --cc=arnd@arndb.de \
    --cc=hjl.tools@gmail.com \
    --cc=james.hogan@imgtec.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.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).