Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030510Ab2EQW6u (ORCPT ); Thu, 17 May 2012 18:58:50 -0400 Received: from mail-wi0-f178.google.com ([209.85.212.178]:51041 "EHLO mail-wi0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760557Ab2EQW6s (ORCPT ); Thu, 17 May 2012 18:58:48 -0400 MIME-Version: 1.0 In-Reply-To: <4FB581D5.9010606@zytor.com> References: <1337292816-10839-1-git-send-email-hjl.tools@gmail.com> <1337292816-10839-2-git-send-email-hjl.tools@gmail.com> <4FB57EB2.4050208@zytor.com> <4FB581D5.9010606@zytor.com> From: Linus Torvalds Date: Thu, 17 May 2012 15:58:26 -0700 X-Google-Sender-Auth: IuaRBgn5Letr9Op1K-XCW_d-xkc Message-ID: Subject: Re: [PATCH 01/10] Use __kernel_long_t in struct timex To: "H. Peter Anvin" Cc: "H.J. Lu" , linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, mingo@kernel.org, tglx@linutronix.de Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 659 Lines: 18 On Thu, May 17, 2012 at 3:55 PM, H. Peter Anvin wrote: > > I would suggest __slong and __ulong then, to keep with the __[su]* > namespace, or does the extra "s" look too much like crap? I do think I could live with it. Maybe we can make x32 do typedef __s64 __slong; typedef __u64 __ulong; and at least not make the "we're declaring a 'long' as a 'long long'"? Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/