From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Komal Bajaj <quic_kbajaj@quicinc.com>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v4 2/6] dt-bindings: cache: qcom,llcc: Add LLCC compatible for QDU1000/QRU1000
Date: Fri, 23 Jun 2023 18:37:42 +0200 [thread overview]
Message-ID: <b44b71d2-949f-8ae3-7369-4430e78de3ec@linaro.org> (raw)
In-Reply-To: <20230623141806.13388-3-quic_kbajaj@quicinc.com>
On 23/06/2023 16:18, Komal Bajaj wrote:
> Add LLCC compatible for QDU1000/QRU1000 SoCs and add optional
> nvmem-cells and nvmem-cell-names property.
Your commit should explain why you are doing this. I can easily see from
the diff that you add nvmem-cells. But why?
>
> Signed-off-by: Komal Bajaj <quic_kbajaj@quicinc.com>
> ---
> Documentation/devicetree/bindings/cache/qcom,llcc.yaml | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-06-23 16:38 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 14:18 [PATCH v4 0/6] soc: qcom: llcc: Add support for QDU1000/QRU1000 Komal Bajaj
2023-06-23 14:18 ` [PATCH v4 1/6] dt-bindings: nvmem: sec-qfprom: Add bindings for secure qfprom Komal Bajaj
2023-06-23 16:36 ` Krzysztof Kozlowski
2023-06-26 8:22 ` Komal Bajaj
2023-06-26 8:30 ` Krzysztof Kozlowski
[not found] ` <c8909dcb-143c-c2d7-513d-625e9ce00c0c@quicinc.com>
2023-06-26 9:46 ` Krzysztof Kozlowski
2023-06-26 10:08 ` Komal Bajaj
2023-06-23 14:18 ` [PATCH v4 2/6] dt-bindings: cache: qcom,llcc: Add LLCC compatible for QDU1000/QRU1000 Komal Bajaj
2023-06-23 16:37 ` Krzysztof Kozlowski [this message]
2023-06-23 14:18 ` [PATCH v4 3/6] nvmem: sec-qfprom: Add Qualcomm secure QFPROM support Komal Bajaj
2023-06-23 14:53 ` Konrad Dybcio
2023-06-27 8:34 ` Komal Bajaj
2023-06-30 20:03 ` Bjorn Andersson
2023-06-24 1:06 ` kernel test robot
2023-06-30 20:14 ` Bjorn Andersson
2023-06-23 14:18 ` [PATCH v4 4/6] soc: qcom: llcc: Refactor llcc driver to support multiple configuration Komal Bajaj
2023-06-23 14:18 ` [PATCH v4 5/6] soc: qcom: Add LLCC support for multi channel DDR Komal Bajaj
2023-06-23 14:26 ` Dmitry Baryshkov
[not found] ` <db8ea67e-529c-856b-026e-2435a2405f6b@quicinc.com>
2023-06-28 13:14 ` Dmitry Baryshkov
2023-06-30 13:54 ` Komal Bajaj
2023-06-23 14:58 ` Konrad Dybcio
2023-06-28 8:52 ` Komal Bajaj
2023-06-28 11:13 ` Konrad Dybcio
2023-06-30 13:51 ` Komal Bajaj
2023-06-30 20:40 ` Bjorn Andersson
2023-06-23 14:18 ` [PATCH v4 6/6] soc: qcom: llcc: Add QDU1000 and QRU1000 LLCC support Komal Bajaj
2023-06-23 14:27 ` Dmitry Baryshkov
2023-06-28 8:53 ` Komal Bajaj
2023-06-23 14:59 ` Konrad Dybcio
2023-06-30 20:45 ` [PATCH v4 0/6] soc: qcom: llcc: Add support for QDU1000/QRU1000 Bjorn Andersson
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=b44b71d2-949f-8ae3-7369-4430e78de3ec@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_kbajaj@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@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).