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 1/2] dt-bindings: arm: qcom,ids: Add SoC ID for SA8650P
Date: Sat, 21 Mar 2026 20:32:39 +0100 [thread overview]
Message-ID: <f619fcbf-8d43-4606-94b2-61b52c24920c@kernel.org> (raw)
In-Reply-To: <cff35ebb2a9bc94ed2381f4ddda7b62d82d4d561.camel@redhat.com>
On 21/03/2026 16:12, Radu Rendec wrote:
> On Sat, 2026-03-21 at 11:03 +0100, Krzysztof Kozlowski wrote:
>> On 20/03/2026 21:59, 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>
>>
>> Please keep consistent spelling of identities. Not sure where the
>> mistake was done - either by Lei or you added his SoB?
>
> Yes, sorry, my bad! By the time I realized what I did, I had already
> sent it. I'll send out v2 shortly.
Does that mean there was no original Signed-off-by? If so, you should
not add it, because you cannot certify for someone else.
Please explain the origins of this patch.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-21 19:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 20:59 [PATCH 0/2] Add Qualcomm SA8650P SoC to socinfo Radu Rendec
2026-03-20 20:59 ` [PATCH 1/2] dt-bindings: arm: qcom,ids: Add SoC ID for SA8650P Radu Rendec
2026-03-21 6:59 ` Dmitry Baryshkov
2026-03-21 10:03 ` Krzysztof Kozlowski
2026-03-21 15:12 ` Radu Rendec
2026-03-21 19:32 ` Krzysztof Kozlowski [this message]
2026-03-22 1:17 ` Radu Rendec
2026-03-20 20:59 ` [PATCH 2/2] soc: qcom: socinfo: " Radu Rendec
2026-03-21 6:59 ` 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=f619fcbf-8d43-4606-94b2-61b52c24920c@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 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.