From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 31C7AC433FE for ; Fri, 4 Nov 2022 14:06:10 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231478AbiKDOGJ (ORCPT ); Fri, 4 Nov 2022 10:06:09 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52160 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229950AbiKDOGI (ORCPT ); Fri, 4 Nov 2022 10:06:08 -0400 Received: from mail-qk1-x72c.google.com (mail-qk1-x72c.google.com [IPv6:2607:f8b0:4864:20::72c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A455322BF7 for ; Fri, 4 Nov 2022 07:06:07 -0700 (PDT) Received: by mail-qk1-x72c.google.com with SMTP id f8so3091656qkg.3 for ; Fri, 04 Nov 2022 07:06:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=uonN8nLloddhG+zjfTG2JodcK/vkMjXLFVPtg7RTwWU=; b=bHUgrJDiiUPKvAYNL1QAYnKS5yc0NP9689zoDl0d5eH4u/GM81pa/AzAmScwJv27HK sWENEgZ2Vs+ikknRhHhgc55AM+hm6KxgSklQKahiOMHgTraJMHF4SVLNqaWUvqwU6B8o jy63ynU8txB7Ri1NmClyahI84lm3Jt+0ClQ90+VMms7DIediHZvbU1b3ezGgm7fsHhhM p6yjhcXSs2xQZ4/WDr41xpQdlAXaZEbATINjKouS+hEjI+FmqG9whzslaTJqQJOzQJkh 4dcA56xqp+l3v8+lSlkcEJpZcdLOjpL73K/qyoHs2kLOsyuIuu/wUra+6Zbg5NMIYr4e dqVw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=uonN8nLloddhG+zjfTG2JodcK/vkMjXLFVPtg7RTwWU=; b=I81gph9z/dnA3VDs3o+BxhgLU7G4ULCr/y+4y9YAwk3iuxAcuM8+yPqa1+p6rOPr7w CZLRL8NuWmVz0h4WvfnHDgZpZc9pZPG6Y8FVqp9qKCquHeaeKLA7rpHsz4l7e8eN6QO/ S2cdn0NkkA/nP+iazk5VLyqrzXNuJ5WUULmKKEmkC8BF2GX9TcDgKaFjaVjkFGqUN2OF 6KddW2rTApGycJ2hyYp/+QqPhpSDSHKrTz+BVvZRimRvEsTXAVqcAp4wMOHvzo1Pa0zF ADKq5pkJL1YswBoe0RbnV2TOsFtykA1VKGqEIVLUkFrl1KkNucjlHoYB2+iYL4HO1mDf +DwQ== X-Gm-Message-State: ACrzQf3igJ5pgOQFU5wvDsKkirphP10f4p/A3Qa5HJnH0+flVBjrcnec 4NBQbAmxS01EjHXVugDyBfUj2Q== X-Google-Smtp-Source: AMsMyM5bwGeqbh2zIZuzZH/uSQDVIlrHtpKBpppr2G3iSgh4BjF2kRkQwYGsZb0VStA7G0pHxGsQpA== X-Received: by 2002:ae9:f406:0:b0:6fa:395d:1480 with SMTP id y6-20020ae9f406000000b006fa395d1480mr17884072qkl.555.1667570766756; Fri, 04 Nov 2022 07:06:06 -0700 (PDT) Received: from ?IPV6:2601:586:5000:570:aad6:acd8:4ed9:299b? ([2601:586:5000:570:aad6:acd8:4ed9:299b]) by smtp.gmail.com with ESMTPSA id y18-20020a05620a25d200b006fa32a26433sm3067660qko.38.2022.11.04.07.06.05 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 04 Nov 2022 07:06:06 -0700 (PDT) Message-ID: <2d4069f6-2c61-15e6-a7f8-64bddfc9fc1e@linaro.org> Date: Fri, 4 Nov 2022 10:06:04 -0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Subject: Re: [PATCH] dt-bindings: qcom: add another exception to the device naming rule Content-Language: en-US To: Dmitry Baryshkov , Andy Gross , Bjorn Andersson , Konrad Dybcio , Rob Clark , Sean Paul , Abhinav Kumar , Rob Herring , Krzysztof Kozlowski Cc: Stephen Boyd , David Airlie , Daniel Vetter , linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org, freedreno@lists.freedesktop.org, Loic Poulain References: <20221104132316.1028137-1-dmitry.baryshkov@linaro.org> From: Krzysztof Kozlowski In-Reply-To: <20221104132316.1028137-1-dmitry.baryshkov@linaro.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On 04/11/2022 09:23, Dmitry Baryshkov wrote: > The 'qcom,dsi-ctrl-6g-qcm2290' compatibility string was added in the > commit ee1f09678f14 ("drm/msm/dsi: Add support for qcm2290 dsi > controller") in February 2022, but was not properly documented in the > bindings. Adding this compatibility string to > display/msm/dsi-controller-main.yaml caused a warning from > qcom-soc.yaml. Fix the warning by adding an exception to the mentioned > file. > > Signed-off-by: Dmitry Baryshkov > --- > Documentation/devicetree/bindings/arm/qcom-soc.yaml | 1 + > 1 file changed, 1 insertion(+) Thanks Dmitry! Reviewed-by: Krzysztof Kozlowski Best regards, Krzysztof