Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 3 Sep 2002 11:51:58 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 3 Sep 2002 11:51:57 -0400 Received: from neon-gw-l3.transmeta.com ([63.209.4.196]:44294 "EHLO neon-gw.transmeta.com") by vger.kernel.org with ESMTP id ; Tue, 3 Sep 2002 11:51:57 -0400 Date: Tue, 3 Sep 2002 09:04:19 -0700 (PDT) From: Linus Torvalds To: Neil Brown cc: Benjamin LaHaise , Pavel Machek , Peter Chubb , , "David S. Miller" Subject: Re: Large block device patch, part 1 of 9 In-Reply-To: <15732.34929.657481.777572@notabene.cse.unsw.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 804 Lines: 23 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. Of course, the really _best_ option would be to have gcc's printf string format be extensible and dynamic. Davem, is sparc64 "long long" 64-bit? 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/