Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 3 Sep 2002 12:19:13 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 3 Sep 2002 12:19:13 -0400 Received: from ns.suse.de ([213.95.15.193]:14355 "EHLO Cantor.suse.de") by vger.kernel.org with ESMTP id ; Tue, 3 Sep 2002 12:19:11 -0400 To: Linus Torvalds Cc: linux-kernel@vger.kernel.org Subject: Re: Large block device patch, part 1 of 9 References: <15732.34929.657481.777572@notabene.cse.unsw.edu.au.suse.lists.linux.kernel> From: Andi Kleen Date: 03 Sep 2002 18:23:43 +0200 In-Reply-To: Linus Torvalds's message of "3 Sep 2002 18:07:05 +0200" Message-ID: X-Mailer: Gnus v5.7/Emacs 20.6 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 917 Lines: 17 Linus Torvalds writes: > On Tue, 3 Sep 2002, Neil Brown wrote: > > > > Effectively, this is a type-safe cast. You still get the warning, but > > it looks more like the C that we are used to. > > I wonder if the right answer isn't to just make things like "__u64" be > "long long" even on 64-bit architectures (at least those on which it is 64 > bit, of course. I _think_ that's true of all of them). And then just use > "llu" for it all. x86-64 does that already. I did it originally to fix some printk warnings. But it caused even more. I didn't bother then to change it back. Doesn't seem to have too many bad side effects at least. -Andi - 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/