From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1768258Ab2KOPKe (ORCPT ); Thu, 15 Nov 2012 10:10:34 -0500 Received: from terminus.zytor.com ([198.137.202.10]:51204 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1768222Ab2KOPKd (ORCPT ); Thu, 15 Nov 2012 10:10:33 -0500 Message-ID: <50A505D4.1080606@zytor.com> Date: Thu, 15 Nov 2012 07:10:12 -0800 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121029 Thunderbird/16.0.2 MIME-Version: 1.0 To: Arnd Bergmann CC: "H.J. Lu" , linux-arch@vger.kernel.org, Vineet.Gupta1@synopsys.com, linux-kernel@vger.kernel.org, James Hogan Subject: Re: new architectures, time_t __kernel_long_t References: <201211141218.02105.arnd@arndb.de> <201211150914.22835.arnd@arndb.de> <201211151436.23088.arnd@arndb.de> In-Reply-To: <201211151436.23088.arnd@arndb.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.