From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Aditya Choudhury <mail@inferno0230.in>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Abel Vesa <abelvesa@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] soc: qcom: Add SoC ID for SM7550
Date: Fri, 13 Nov 2026 15:42:25 +0100 [thread overview]
Message-ID: <21a22750-2586-429b-9179-da3548c6c3f9@oss.qualcomm.com> (raw)
In-Reply-To: <avcgXkYgdjpfnfbZ@mediaserver>
On 11/13/26 3:36 PM, Aditya Choudhury wrote:
> On Fri, Nov 13, 2026 at 09:12:24AM +0100, Konrad Dybcio wrote:
>> On 11/12/26 11:30 AM, Aditya Choudhury wrote:
>>> Add the SoC ID for the Qualcomm SM7550 (codename "crow" in downstream) to the
>>> dt-bindings header and the socinfo table.
>>
>> Please use the real codename of Camano for the following
>> submissions
>
> Thanks for letting me know. I'll adapt my patches to use
> camano instead.
>
> Should I also send a v2 of this series with the codename
> corrected from crow to Camano?
The current commit message on this patch is accurate - downstream
calls it crow
Konrad
prev parent reply other threads:[~2026-11-13 14:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 10:30 Aditya Choudhury
2026-11-12 10:30 ` [PATCH 1/2] dt-bindings: arm: qcom,ids: " Aditya Choudhury
2026-11-13 8:13 ` Konrad Dybcio
2026-11-13 11:17 ` Krzysztof Kozlowski
2026-11-13 14:30 ` Aditya Choudhury
2026-11-13 14:57 ` Krzysztof Kozlowski
2026-11-13 15:59 ` Aditya Choudhury
2026-11-12 10:30 ` [PATCH 2/2] soc: qcom: socinfo: " Aditya Choudhury
2026-11-13 11:17 ` Krzysztof Kozlowski
2026-11-13 8:12 ` [PATCH 0/2] soc: qcom: " Konrad Dybcio
2026-11-13 14:36 ` Aditya Choudhury
2026-11-13 14:42 ` Konrad Dybcio [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=21a22750-2586-429b-9179-da3548c6c3f9@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=abelvesa@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=mail@inferno0230.in \
--cc=robh@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
all inboxes | Powered by JetHome®