From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 41xJ3v5x5HzDq5k for ; Fri, 24 Aug 2018 07:50:03 +1000 (AEST) Message-ID: <4557653efa685ffc0533f7168a628491ad843e01.camel@kernel.crashing.org> Subject: Re: DT case sensitivity From: Benjamin Herrenschmidt To: Segher Boessenkool Cc: Rob Herring , Stephen Rothwell , Grant Likely , Michael Ellerman , Kumar Gala , David Gibson , Frank Rowand , devicetree-spec@vger.kernel.org, devicetree@vger.kernel.org, linuxppc-dev Date: Fri, 24 Aug 2018 07:49:19 +1000 In-Reply-To: <20180823121929.GS24439@gate.crashing.org> References: <3335cff2cc999c1dda58d75949ab3d12185fca79.camel@kernel.crashing.org> <20180823121929.GS24439@gate.crashing.org> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Thu, 2018-08-23 at 07:19 -0500, Segher Boessenkool wrote: > If one implementation does case insensitive, it will most likely just work, > because people do not make insane names differing only in case on purpose. Apple did :-) ide, vs IDE, ata vs ATA, I've seen all sort of crap there, esp. on old machines. > Now people write other things that they only test against that implementation, > and those things now only work with case-insensitive. And you do not know > without testing if anything breaks. (But the laws of big numbers are against > you here). Since there isn't really a drawback to doing case-insensitive > always, that is a much safer way forward, much less work for everyone, even > if technically the wrong thing to do :-) > > > Segher