Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758574AbYJQP4s (ORCPT ); Fri, 17 Oct 2008 11:56:48 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755702AbYJQPzl (ORCPT ); Fri, 17 Oct 2008 11:55:41 -0400 Received: from smtp1.linux-foundation.org ([140.211.169.13]:37942 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758118AbYJQPzk (ORCPT ); Fri, 17 Oct 2008 11:55:40 -0400 Date: Fri, 17 Oct 2008 08:54:37 -0700 (PDT) From: Linus Torvalds To: Benjamin Herrenschmidt cc: David Miller , rdreier@cisco.com, Geert.Uytterhoeven@sonycom.com, hpa@zytor.com, linux-kernel@vger.kernel.org, mingo@elte.hu, yhlu.kernel@gmail.com, akpm@linux-foundation.org Subject: Re: [PATCH] Fix broken debug output reserve_region_with_split() In-Reply-To: <1224220339.7654.84.camel@pasglop> Message-ID: References: <1224214314.7654.65.camel@pasglop> <20081016.210404.151891223.davem@davemloft.net> <1224220339.7654.84.camel@pasglop> User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 849 Lines: 39 On Fri, 17 Oct 2008, Benjamin Herrenschmidt wrote: > > +#ifdef CONFIG_PHYS_ADDR_T_64BIT > +#define MEM_RSRC_SIZE 16 > +#else > +#define MEM_RSRC_SIZE 8 > +#endif > + > +#ifdef CONFIG_X86 > +#define IO_RSRC_SIZE 4 > +#elif CONFIG_PPC > +#define IO_RSRC_SIZE 8 > +#else > +#define IO_RSRC_SIZE MEM_RSRC_SIZE > +#endif Why? Do you think alpha wants to see its PIO resources shown as [00000000000001f0-00000000000001f7] or [01f0-01f7] and which do you think is more readable? And even on sparc, with the full 64 bits in use, it's not like we'd be *truncating* to 4 hex digits with %04x. 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/