From: Krzysztof Kozlowski <krzk@kernel.org>
To: Radu Rendec <rrendec@redhat.com>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Cc: Lei wang <quic_leiwan@quicinc.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Subject: Re: [PATCH v2 1/2] dt-bindings: arm: qcom,ids: Add SoC ID for SA8650P
Date: Sun, 22 Mar 2026 09:50:50 +0100 [thread overview]
Message-ID: <c8ffbdde-a01c-4793-b7ad-c056983b231c@kernel.org> (raw)
In-Reply-To: <6a1260a8-8988-4839-a7a3-edb9a1bf71fa@kernel.org>
On 21/03/2026 20:33, Krzysztof Kozlowski wrote:
> On 21/03/2026 20:29, Krzysztof Kozlowski wrote:
>> On 21/03/2026 16:23, Radu Rendec wrote:
>>> From: Lei wang <quic_leiwan@quicinc.com>
>>>
>>> Add unique ID for Qualcomm SA8650P SoC.
>>>
>>> Signed-off-by: Lei wang <quic_leiwan@quicinc.com>
>>> Signed-off-by: Radu Rendec <rrendec@redhat.com>
>>> ---
>>
>>
>> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
>>
>> <form letter>
>> This is a friendly reminder during the review process.
>>
>
> And I read now answer to v1, so the DCO and patch provenance still needs
> clarifications.
It's fine, SoB now matches original patch.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-22 8:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-21 15:23 [PATCH v2 0/2] Add Qualcomm SA8650P SoC to socinfo Radu Rendec
2026-03-21 15:23 ` [PATCH v2 1/2] dt-bindings: arm: qcom,ids: Add SoC ID for SA8650P Radu Rendec
2026-03-21 19:29 ` Krzysztof Kozlowski
2026-03-21 19:33 ` Krzysztof Kozlowski
2026-03-22 8:50 ` Krzysztof Kozlowski [this message]
2026-03-21 15:23 ` [PATCH v2 2/2] soc: qcom: socinfo: " Radu Rendec
2026-03-21 19:30 ` Krzysztof Kozlowski
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=c8ffbdde-a01c-4793-b7ad-c056983b231c@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_leiwan@quicinc.com \
--cc=robh@kernel.org \
--cc=rrendec@redhat.com \
/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