Received: by 2002:a05:6a10:1a4d:0:0:0:0 with SMTP id nk13csp143360pxb; Mon, 31 Jan 2022 17:41:23 -0800 (PST) X-Google-Smtp-Source: ABdhPJx+27kfHTqhVTcMT4ASZiaaMc4DenJ5g5aEGACaNvbdiwDV/ysP/XhHlWSoIBK02GIcJouk X-Received: by 2002:a17:906:58d4:: with SMTP id e20mr19413383ejs.258.1643679682897; Mon, 31 Jan 2022 17:41:22 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643679682; cv=none; d=google.com; s=arc-20160816; b=gJGaqZWplFZ4CYopsooeaYk5+hBwfhOsBszMNTjOPOCSQL/CZ08EKA6UTKeyDQwVvW 2irYA4xI3+JebdDWam+/THCqn3y95aTh4VU4Kx361TDwJplx/KnMD/fblkuVWmbdENEz Whv/rBNlE1sc8zbIxWQmOJjpAicEfwuNNbESvFE6T3di29Y0xdoHNw3rAdLGPfZ9yV57 lPIakSAMwAHXsXBHuSrhDMRH2rCDMVy8soyZc0G0MHlKr0PV3xqEfQ0ly2IAe0kIAdaU zzNgUr0tG85XZERrnM+1OBcFPJwuhD0jp9i2Pc2/TWhkXDZnSpaq5MAMYXkE0dkjjl3K qhhg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=yJctG/WbEKzDt8UjZPmXGGg6sG2I4y+2xmJx4o9NfIM=; b=kY3xVHwEFXRf/cvLzzy6A6Hx+7Mb9CXZXxfET7iUfBWbAqgjDQg9ZwCxgXMnxMqBJ5 2b2DloSMOmo2DmLP3vhQG2eENfTFuO0oli0d3Oj9H5Q+CAr0pRHB4bB8LGRTy3o9yvn+ f+s2RbPR4H4KEAPhefyshw7Bl+xj/w9seIzNopZOY2cTdFRo8PYdL/OpVjH+cKnqjn8j UYOP6JpI7aX7P9bpV3cuy4JupmyxmrIFxyYe6DgVMhl8Ln8k0OXbsZILAUsBAyh4y6Un 9dwpdwktdGsR1x2psaosSYCnm1IVnrpAk5o0KItU+3QzHW/OrhkUKCBlqUQteTPn+H2W /aAg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@canonical.com header.s=20210705 header.b=I3xRoTfx; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=canonical.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id j6si8294929ejo.751.2022.01.31.17.40.58; Mon, 31 Jan 2022 17:41:22 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@canonical.com header.s=20210705 header.b=I3xRoTfx; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=canonical.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230130AbiA2KeZ (ORCPT + 99 others); Sat, 29 Jan 2022 05:34:25 -0500 Received: from smtp-relay-internal-0.canonical.com ([185.125.188.122]:52280 "EHLO smtp-relay-internal-0.canonical.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229837AbiA2KeV (ORCPT ); Sat, 29 Jan 2022 05:34:21 -0500 Received: from mail-ed1-f69.google.com (mail-ed1-f69.google.com [209.85.208.69]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by smtp-relay-internal-0.canonical.com (Postfix) with ESMTPS id 53B564000F for ; Sat, 29 Jan 2022 10:34:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=canonical.com; s=20210705; t=1643452460; bh=yJctG/WbEKzDt8UjZPmXGGg6sG2I4y+2xmJx4o9NfIM=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=I3xRoTfxNDGsJcXo0szCLhBJfbVhMZ9iSkx0Yto1VvHYeQVMqyotVJ0dgI7icgPsi ziZjc1BFonMY5YXoZRoZfEtM+i8JxZJd8V6bXY0vShlDZ3YBZR0sYQ8Fpq6VajrW6G Er4INuKJHvmFdjtW6eCpgH4FW/lbcd/W6/YLCemxcd7FuwJMiGH68uqiPRM/+U9ajR 4Ltg7tcXEeaUu4Y+0zFMKG6FEx0r7AyZyTd33+q4nzWqC/E5gSuVSgtQqP1305Q++4 ztM0u/U5Ji/YinaMkwQ+Cz9UqiCgY+6txTwcbLBrZBpjr52sRtfE2STzpt9V7ejCg3 eBftnpQFsU9tA== Received: by mail-ed1-f69.google.com with SMTP id ed6-20020a056402294600b004090fd8a936so4328471edb.23 for ; Sat, 29 Jan 2022 02:34:20 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=yJctG/WbEKzDt8UjZPmXGGg6sG2I4y+2xmJx4o9NfIM=; b=1FoLcsvsz1bO7moVwGydXhY6pFZBPGOhrgom6kFg1dc6ieqRZYfXEA1S9xMg9TowSv KhZDp2U3K9lwFa963ADpXzjFiqQbmH+QK6XRTe6jojQyqB3uYtqv6NrgFej/fG41CFz8 IEcQryjYO3wUL/Ke/0n8hdjiEApIySNUUt5E0wy97bTHS8otx/FjnSvniMZce8JUssQ2 mgrUghPI1/bjhzNaxzg33eOB81LZ6ILYFbP1/+rQpx9QnHpSQQg+Fxmcz/pNR0/fjtSv iANfG/QVujWDqddQNdHAyTL315uGVBnMixbTXEgkw+ocPx0hdunNSp7RRqNaWWGi9KuS J65Q== X-Gm-Message-State: AOAM531Jxv7trLYGlXXTxmXa7CQn5qWQydVBuDkcnLiwlPluusXn7GWS dYXQx3gfaoUdvcmoWRCGpnbSw+0qBb8HYb7J5CvgNy9Mck3F6nwTbPSryIPQAtEdEMl7kfmRO1N DlGv4LAlLNuYoOItcuiq4KdMNGRJLNnh2RTFqrZ10sA== X-Received: by 2002:a17:907:8689:: with SMTP id qa9mr9922382ejc.512.1643452459802; Sat, 29 Jan 2022 02:34:19 -0800 (PST) X-Received: by 2002:a17:907:8689:: with SMTP id qa9mr9922375ejc.512.1643452459621; Sat, 29 Jan 2022 02:34:19 -0800 (PST) Received: from [192.168.0.70] (xdsl-188-155-168-84.adslplus.ch. [188.155.168.84]) by smtp.gmail.com with ESMTPSA id j25sm2104650edp.10.2022.01.29.02.34.18 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 29 Jan 2022 02:34:18 -0800 (PST) Message-ID: Date: Sat, 29 Jan 2022 11:34:17 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: [PATCH 6/8] dt-bindings: vendor-prefixes: add LG Electronics Content-Language: en-US To: Luca Weiss , Petr Vorel , linux-arm-msm@vger.kernel.org, Rob Herring Cc: Shawn Guo , Oleksij Rempel , Sam Ravnborg , Linus Walleij , Daniel Palmer , Max Merchel , Hao Fang , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Jean THOMAS References: <5883435.31r3eYUQgx@g550jk> <64ee2334-aa99-7226-8946-84c95676041a@canonical.com> <3398674.ElGaqSPkdT@g550jk> From: Krzysztof Kozlowski In-Reply-To: <3398674.ElGaqSPkdT@g550jk> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 29/01/2022 10:45, Luca Weiss wrote: > Hi Krzysztof, > >>>>> >>>>> Have we sorted this lg- vs. lge- ? >>>>> >>>>> There are both: >>>>> arch/arm/boot/dts/qcom-msm8974-lge-nexus5-hammerhead.dts >>>>> vs >>>>> arch/arm/boot/dts/qcom-apq8026-lg-lenok.dts >>>> >>>> Probably renaming/unifying/correcting prefix in existing compatibles is >>>> not worth the effort. This would make a mess and affect other DTS users. >>> >>> If wanted I can send a patch renaming the Nexus 5 to just LG, this would >>> adjust both compatible in the file (which shouldn't really affect >>> anything) and the filename (which probably will affect various scripts >>> and whatnot used by existing users of the dtb). >>> Is this something that can be done in mainline or should we rather just >>> let it be? I'm not sure what the policies there are. >> >> The "lge" compatible is already in the bindings, so it should not be >> changed without valid reason. Imagine there is an user-space code >> parsing compatibles to adjust some power-management settings to >> different models. It would be broken now. >> >> What could be done is to mark it as deprecated and a add new one: >> compatible = "lg,hammerhead", "lge,hammerhead", "qcom,msm8974"; >> This should be safe for user-space and allow transition to common "lg". > > What can or should be done about the filename then? I don't have an opinion on the filename. It does not matter to me. :) You can change it to "lg" or keep "lge". I don't see much benefits of changing it but I don't mind keeping it consistent. Best regards, Krzysztof