From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from jdl.com (jdl.com [208.123.74.7]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id 18D1CDDE17 for ; Mon, 22 Oct 2007 22:37:04 +1000 (EST) To: Segher Boessenkool Subject: Re: [PATCH 4/4] DTC: Begin the path to sane literals and expressions. In-Reply-To: Your message of "Sun, 21 Oct 2007 07:30:45 +0200." <20d6133a9294d4f06a7e78ca627ec4f3@kernel.crashing.org> References: <20d6133a9294d4f06a7e78ca627ec4f3@kernel.crashing.org> Date: Mon, 22 Oct 2007 07:36:57 -0500 From: Jon Loeliger Message-Id: Cc: linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , So, like, the other day Segher Boessenkool mumbled: > > Property names have been limited to start with > > characters from the set [a-zA-Z,._#?]. That is, the > > digits and the expression symbols have been removed. > > This cannot work; many property names start with a digit, > for example. Are any of those property names in use in any of our DTS files or b-w-o.txt? Not really, no. In fact, with this lexical change, all of our DTS files still produce byte-identical results. I really think this is one of those areas where we may need to stray from the other guideline. Is there a compelling reason somewhere? Really? jdl