Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Tue, 8 Nov 2022 09:50:58 +0530
From:   Viresh Kumar <viresh.kumar@linaro.org>
To:     Serge Semin <Sergey.Semin@baikalelectronics.ru>
Cc:     Viresh Kumar <vireshk@kernel.org>, Nishanth Menon <nm@ti.com>,
        Stephen Boyd <sboyd@kernel.org>,
        Rob Herring <robh+dt@kernel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
        Maxime Ripard <maxime@cerno.tech>,
        Serge Semin <fancer.lancer@gmail.com>,
        Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>,
        Pavel Parkhomenko <Pavel.Parkhomenko@baikalelectronics.ru>,
        Rob Herring <robh@kernel.org>, linux-pm@vger.kernel.org,
        devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: opp-v2: Fix clock-latency-ns prop in example
Message-ID: <20221108042058.o7xuzkuokykv5xcs@vireshk-i7>
References: <20221107204355.31971-1-Sergey.Semin@baikalelectronics.ru>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20221107204355.31971-1-Sergey.Semin@baikalelectronics.ru>
Precedence: bulk

On 07-11-22, 23:43, Serge Semin wrote:
> Accidentally discovered a hidden typo in the DT-nodes defined in the
> opp-v2 bindings example. Instead of specifying the "clock-latency-ns"
> property the DT-node has been created with the "lock-latency-ns" property
> in it, which doesn't exist neither in opp-v2 nor in the base schemas.
> Let's fix the name to having the "clock-" prefix as it was originally
> implied and as the rest of the similar nodes has.
> 
> Fixes: 94274f20f6bf ("dt-bindings: opp: Convert to DT schema")
> Signed-off-by: Serge Semin <Sergey.Semin@baikalelectronics.ru>

Applied. Thanks.

-- 
viresh