From: Stephen Boyd <sboyd@kernel.org>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Ilia Lin <ilia.lin@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Nishanth Menon <nm@ti.com>, Rob Herring <robh+dt@kernel.org>,
Viresh Kumar <vireshk@kernel.org>,
Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH 1/2] dt-bindings: clock: qcom,sm8450-camcc: constrain required-opps
Date: Fri, 20 Jan 2023 14:15:06 -0800 [thread overview]
Message-ID: <b676c36565da1b73c53ced6218ef6de1.sboyd@kernel.org> (raw)
In-Reply-To: <20230119130028.106817-1-krzysztof.kozlowski@linaro.org>
Quoting Krzysztof Kozlowski (2023-01-19 05:00:27)
> Be specific how many required-opps are allowed.
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>
> ---
>
> This change is independent, although logically is connected with my
> dtschema pull:
> https://github.com/devicetree-org/dt-schema/pull/95
Do you want to take it through dt tree?
next prev parent reply other threads:[~2023-01-20 22:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 13:00 [PATCH 1/2] dt-bindings: clock: qcom,sm8450-camcc: constrain required-opps Krzysztof Kozlowski
2023-01-19 13:00 ` [PATCH 2/2] dt-bindings: opp: " Krzysztof Kozlowski
2023-01-20 4:38 ` Viresh Kumar
2023-01-20 6:27 ` Krzysztof Kozlowski
2023-01-20 6:41 ` Krzysztof Kozlowski
2023-01-20 22:15 ` Stephen Boyd [this message]
2023-01-21 18:59 ` [PATCH 1/2] dt-bindings: clock: qcom,sm8450-camcc: " Krzysztof Kozlowski
2023-01-25 20:32 ` Stephen Boyd
2023-01-23 21:18 ` Rob Herring
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b676c36565da1b73c53ced6218ef6de1.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ilia.lin@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=vireshk@kernel.org \
--cc=vladimir.zapolskiy@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).