From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>,
linux-arm-msm@vger.kernel.org, andersson@kernel.org,
agross@kernel.org
Cc: patches@linaro.org, Konrad Dybcio <konrad.dybcio@somainline.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Manivannan Sadhasivam <mani@kernel.org>,
linux-remoteproc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: remoteproc: qcom,adsp: Add SM6375 ADSP and CDSP
Date: Mon, 12 Dec 2022 10:16:04 +0100 [thread overview]
Message-ID: <f7cb79d2-cfcf-dd12-5127-373ed192120e@linaro.org> (raw)
In-Reply-To: <be450f51-6e1c-a3c1-904f-1f915f0dba5e@linaro.org>
On 10/11/2022 10:32, Krzysztof Kozlowski wrote:
> On 09/11/2022 18:08, Konrad Dybcio wrote:
>> Add entries for SM6375 ADSP and CDSP. They are effectively the same
>> as SM6350 ADSP and SM8150 CDSP respectively.
>>
>> Signed-off-by: Konrad Dybcio <konrad.dybcio@linaro.org>
>> ---
>> .../devicetree/bindings/remoteproc/qcom,adsp.yaml | 8 ++++++++
>> 1 file changed, 8 insertions(+)
>>
>
>
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Although change looks ok, but I missed that it will conflict with my
series here:
https://lore.kernel.org/all/20221124184333.133911-1-krzysztof.kozlowski@linaro.org/
This should be moved to a new tile or merged with one of device-specific
bindings I added.
Best regards,
Krzysztof
prev parent reply other threads:[~2022-12-12 9:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 17:08 [PATCH 1/2] dt-bindings: remoteproc: qcom,adsp: Add SM6375 ADSP and CDSP Konrad Dybcio
2022-11-09 17:08 ` [PATCH 2/2] remoteproc: qcom: pas: Add SM6375 ADSP & CDSP Konrad Dybcio
2022-11-10 9:32 ` [PATCH 1/2] dt-bindings: remoteproc: qcom,adsp: Add SM6375 ADSP and CDSP Krzysztof Kozlowski
2022-12-12 9:16 ` Krzysztof Kozlowski [this message]
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=f7cb79d2-cfcf-dd12-5127-373ed192120e@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mani@kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=patches@linaro.org \
--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).