From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Tengfei Fan <quic_tengfan@quicinc.com>,
andersson@kernel.org, konrad.dybcio@linaro.org,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org
Cc: quic_tsoni@quicinc.com, quic_shashim@quicinc.com,
quic_kaushalk@quicinc.com, quic_tdas@quicinc.com,
quic_tingweiz@quicinc.com, quic_aiquny@quicinc.com,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] soc: qcom: socinfo: add SM4450 ID
Date: Wed, 19 Jul 2023 12:26:03 +0200 [thread overview]
Message-ID: <3d544c17-7aa9-bc68-c56d-6b6fad1c7b66@linaro.org> (raw)
In-Reply-To: <185cb945-4c4e-1697-060e-602a3af2fe50@linaro.org>
On 19/07/2023 12:15, Dmitry Baryshkov wrote:
> On 19/07/2023 13:01, Tengfei Fan wrote:
>> Add the ID for the Qualcomm SM4450 SoC.
>>
>> Signed-off-by: Tengfei Fan <quic_tengfan@quicinc.com>
>> ---
>> drivers/soc/qcom/socinfo.c | 1 +
>> include/dt-bindings/arm/qcom,ids.h | 2 ++
>> 2 files changed, 3 insertions(+)
>>
>> diff --git a/drivers/soc/qcom/socinfo.c b/drivers/soc/qcom/socinfo.c
>> index 4d49945b3a35..fa5e4c54207a 100644
>> --- a/drivers/soc/qcom/socinfo.c
>> +++ b/drivers/soc/qcom/socinfo.c
>> @@ -415,6 +415,7 @@ static const struct soc_id soc_id[] = {
>> { qcom_board_id(IPQ5312) },
>> { qcom_board_id(IPQ5302) },
>> { qcom_board_id(IPQ5300) },
>> + { qcom_board_id(SM4450) },
>> };
>>
>> static const char *socinfo_machine(struct device *dev, unsigned int id)
>> diff --git a/include/dt-bindings/arm/qcom,ids.h b/include/dt-bindings/arm/qcom,ids.h
>> index bcbe9ee2cdaf..6201bfb1405e 100644
>> --- a/include/dt-bindings/arm/qcom,ids.h
>> +++ b/include/dt-bindings/arm/qcom,ids.h
>> @@ -2,6 +2,7 @@
>> /*
>> * Copyright (c) 2015, The Linux Foundation. All rights reserved.
>> * Copyright (c) 2022 Linaro Ltd
>> + * Copyright (c) 2023, Qualcomm Innovation Center, Inc. All rights reserved.
>
> I wonder whether a single define is copyrightable.
If you carefully choose a place, like out of order, then probably it is
a creative work. :)
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-07-19 10:27 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 10:01 [PATCH 0/5] soc: qcom: Add support for SM4450 Tengfei Fan
2023-07-19 10:01 ` [PATCH 1/5] arm64: dts: qcom: Add base SM4450 DTSI Tengfei Fan
2023-07-19 10:14 ` Dmitry Baryshkov
2023-07-21 1:53 ` Tengfei Fan
2023-07-19 10:22 ` Krzysztof Kozlowski
2023-07-21 1:59 ` Tengfei Fan
2023-07-20 7:54 ` Konrad Dybcio
2023-07-21 2:03 ` Tengfei Fan
2023-07-19 10:01 ` [PATCH 2/5] arm64: dts: qcom: Add base SM4450 QRD DTS Tengfei Fan
2023-07-19 10:17 ` Dmitry Baryshkov
2023-07-21 2:07 ` Tengfei Fan
2023-07-19 10:23 ` Krzysztof Kozlowski
2023-07-21 2:18 ` Tengfei Fan
2023-07-19 10:01 ` [PATCH 3/5] dt-bindings: firmware: scm: Add SM4450 Tengfei Fan
2023-07-19 10:16 ` Dmitry Baryshkov
2023-07-21 2:19 ` Tengfei Fan
2023-07-19 10:24 ` Krzysztof Kozlowski
2023-07-21 2:19 ` Tengfei Fan
2023-07-19 10:01 ` [PATCH 4/5] dt-bindings: arm: qcom: Document SM4450 SoC and boards Tengfei Fan
2023-07-19 10:15 ` Dmitry Baryshkov
2023-07-21 2:20 ` Tengfei Fan
2023-07-19 10:24 ` Krzysztof Kozlowski
2023-07-21 2:24 ` Tengfei Fan
2023-07-19 10:01 ` [PATCH 5/5] soc: qcom: socinfo: add SM4450 ID Tengfei Fan
2023-07-19 10:15 ` Dmitry Baryshkov
2023-07-19 10:26 ` Krzysztof Kozlowski [this message]
2023-07-21 2:26 ` Tengfei Fan
2023-07-19 10:25 ` Krzysztof Kozlowski
2023-07-21 2:27 ` Tengfei Fan
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=3d544c17-7aa9-bc68-c56d-6b6fad1c7b66@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.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=quic_aiquny@quicinc.com \
--cc=quic_kaushalk@quicinc.com \
--cc=quic_shashim@quicinc.com \
--cc=quic_tdas@quicinc.com \
--cc=quic_tengfan@quicinc.com \
--cc=quic_tingweiz@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).