From: Stephen Boyd <sboyd@kernel.org>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Taniya Das <quic_tdas@quicinc.com>
Cc: linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 03/11] clk: qcom: gcc-msm8974: use ARRAY_SIZE instead of specifying num_parents
Date: Wed, 28 Sep 2022 13:53:39 -0700 [thread overview]
Message-ID: <20220928205341.0740CC433B5@smtp.kernel.org> (raw)
In-Reply-To: <50374fb8-563f-6433-12c9-8ff77fa38e83@linaro.org>
Quoting Neil Armstrong (2022-09-28 08:23:14)
> On 28/09/2022 16:59, Dmitry Baryshkov wrote:
> > Use ARRAY_SIZE() instead of manually specifying num_parents. This makes
> > adding/removing entries to/from parent_data easy and errorproof.
> >
> > Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
>
> Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>
Please trim replies so I don't have to scroll down to the bottom to find
out a single tag was added.
next prev parent reply other threads:[~2022-09-28 20:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 14:59 [PATCH 00/11] clk: qcom: update MSM8974 clock controller drivers Dmitry Baryshkov
2022-09-28 14:59 ` [PATCH 01/11] dt-bindings: clock: split qcom,gcc-msm8974,-msm8226 to the separate file Dmitry Baryshkov
2022-09-28 17:10 ` Krzysztof Kozlowski
2022-09-28 14:59 ` [PATCH 02/11] dt-bindings: clocks: qcom,mmcc: define clocks/clock-names for MSM8974 Dmitry Baryshkov
2022-09-28 17:12 ` Krzysztof Kozlowski
2022-09-28 14:59 ` [PATCH 03/11] clk: qcom: gcc-msm8974: use ARRAY_SIZE instead of specifying num_parents Dmitry Baryshkov
2022-09-28 15:23 ` Neil Armstrong
2022-09-28 20:53 ` Stephen Boyd [this message]
2022-09-28 14:59 ` [PATCH 04/11] clk: qcom: gcc-msm8974: move clock parent tables down Dmitry Baryshkov
2022-09-28 15:22 ` Neil Armstrong
2022-09-28 14:59 ` [PATCH 05/11] clk: qcom: gcc-msm8974: use parent_hws/_data instead of parent_names Dmitry Baryshkov
2022-09-28 14:59 ` [PATCH 06/11] clk: qcom: mmcc-msm8974: use ARRAY_SIZE instead of specifying num_parents Dmitry Baryshkov
2022-09-28 15:25 ` Neil Armstrong
2022-09-28 14:59 ` [PATCH 07/11] clk: qcom: mmcc-msm8974: move clock parent tables down Dmitry Baryshkov
2022-09-28 15:26 ` Neil Armstrong
2022-09-28 14:59 ` [PATCH 08/11] clk: qcom: mmcc-msm8974: use parent_hws/_data instead of parent_names Dmitry Baryshkov
2022-09-28 14:59 ` [PATCH 09/11] ARM: dts: qcom: msm8974: add second DSI host and PHY Dmitry Baryshkov
2022-09-28 17:12 ` Krzysztof Kozlowski
2022-09-28 14:59 ` [PATCH 10/11] ARM: dts: qcom: msm8974: add clocks and clock-names to gcc device Dmitry Baryshkov
2022-09-28 14:59 ` [PATCH 11/11] ARM: dts: qcom: msm8974: add clocks and clock-names to mmcc device Dmitry Baryshkov
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=20220928205341.0740CC433B5@smtp.kernel.org \
--to=sboyd@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=neil.armstrong@linaro.org \
--cc=quic_tdas@quicinc.com \
--cc=robh+dt@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.