Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 1 Nov 2002 15:24:10 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 1 Nov 2002 15:24:10 -0500 Received: from ip68-105-128-224.tc.ph.cox.net ([68.105.128.224]:63148 "EHLO Bill-The-Cat.bloom.county") by vger.kernel.org with ESMTP id ; Fri, 1 Nov 2002 15:24:09 -0500 Date: Fri, 1 Nov 2002 13:30:33 -0700 From: Tom Rini To: Roman Zippel , linux-kernel@vger.kernel.org, Russell King Subject: Re: Where's the documentation for Kconfig? Message-ID: <20021101203033.GA5773@opus.bloom.county> References: <20021031134308.I27461@parcelfarce.linux.theplanet.co.uk> <20021101125226.B16919@flint.arm.linux.org.uk> <20021101193112.B26989@flint.arm.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021101193112.B26989@flint.arm.linux.org.uk> User-Agent: Mutt/1.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 866 Lines: 24 On Fri, Nov 01, 2002 at 07:31:12PM +0000, Russell King wrote: > Ok, next problem. > > A "hex" config entry under the old config language used to omit the "0x" > prefix, requiring it to be added by whatever used it. Kconfig adds the > "0x" prefix, thereby causing errors. > > Is this difference intentional? I would imagine so since it means you don't have to add '0x' in front of things anymore (since IIRC define_hex would allow either previously, fun and hilarity would ensure). On a related question, can we now have 'UL', etc in a hex statement / question? -- Tom Rini (TR1265) http://gate.crashing.org/~trini/ - 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/