From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>,
Sibi Sankar <quic_sibis@quicinc.com>,
andersson@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org
Cc: agross@kernel.org, conor+dt@kernel.org, quic_rjendra@quicinc.com,
abel.vesa@linaro.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
quic_tsoni@quicinc.com, neil.armstrong@linaro.org
Subject: Re: [PATCH V2 1/2] dt-bindings: cache: qcom,llcc: Add X1E80100 compatible
Date: Mon, 20 Nov 2023 11:02:05 +0100 [thread overview]
Message-ID: <50062f55-e516-4bc6-bc06-ddb043532aa8@linaro.org> (raw)
In-Reply-To: <f3cd8531-faa8-4ec4-b1b8-ba327b7df5cd@linaro.org>
On 18/11/2023 00:37, Konrad Dybcio wrote:
> On 17.11.2023 10:53, Sibi Sankar wrote:
>> From: Rajendra Nayak <quic_rjendra@quicinc.com>
>>
>> Add the compatible for X1E80100 platforms.
>>
>> Signed-off-by: Rajendra Nayak <quic_rjendra@quicinc.com>
>> Co-developed-by: Sibi Sankar <quic_sibis@quicinc.com>
>> Signed-off-by: Sibi Sankar <quic_sibis@quicinc.com>
>> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>> ---
> Unrelated to this patch alone, but I noticed that with this new naming
> scheme, patterns in Documentation/devicetree/bindings/arm/qcom-soc.yaml will
> require an update as well.
I'll fix existing platforms.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-11-20 10:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 9:53 [PATCH V2 0/2] cache: qcom,llcc: Add llcc support for X1E80100 Sibi Sankar
2023-11-17 9:53 ` [PATCH V2 1/2] dt-bindings: cache: qcom,llcc: Add X1E80100 compatible Sibi Sankar
2023-11-17 23:37 ` Konrad Dybcio
2023-11-20 6:56 ` Sibi Sankar
2023-11-20 10:02 ` Krzysztof Kozlowski [this message]
2023-11-17 9:53 ` [PATCH V2 2/2] soc: qcom: llcc: Add configuration data for X1E80100 Sibi Sankar
2023-12-08 14:55 ` [PATCH V2 0/2] cache: qcom,llcc: Add llcc support " 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=50062f55-e516-4bc6-bc06-ddb043532aa8@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=abel.vesa@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=neil.armstrong@linaro.org \
--cc=quic_rjendra@quicinc.com \
--cc=quic_sibis@quicinc.com \
--cc=quic_tsoni@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 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).