From: Rob Herring <robh@kernel.org>
To: Kathiravan T <quic_kathirav@quicinc.com>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, quic_saahtoma@quicinc.com
Subject: Re: [PATCH V2 1/2] dt-bindings: arm: qcom,ids: drop the IPQ5019 SoC ID
Date: Fri, 14 Jul 2023 09:59:54 -0600 [thread overview]
Message-ID: <20230714155954.GA3919199-robh@kernel.org> (raw)
In-Reply-To: <20230712041912.398724-2-quic_kathirav@quicinc.com>
On Wed, Jul 12, 2023 at 09:49:11AM +0530, Kathiravan T wrote:
> IPQ5019 SoC is never productized. So lets drop it.
You need to remove the user before removing the definition.
>
> Signed-off-by: Kathiravan T <quic_kathirav@quicinc.com>
> ---
> Changes in V2:
> - Updated the commit message with the precise information for
> dropping this ID
>
> include/dt-bindings/arm/qcom,ids.h | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/include/dt-bindings/arm/qcom,ids.h b/include/dt-bindings/arm/qcom,ids.h
> index bcbe9ee2cdaf..179dd56b2d95 100644
> --- a/include/dt-bindings/arm/qcom,ids.h
> +++ b/include/dt-bindings/arm/qcom,ids.h
> @@ -250,7 +250,6 @@
> #define QCOM_ID_QRU1000 539
> #define QCOM_ID_QDU1000 545
> #define QCOM_ID_QDU1010 587
> -#define QCOM_ID_IPQ5019 569
> #define QCOM_ID_QRU1032 588
> #define QCOM_ID_QRU1052 589
> #define QCOM_ID_QRU1062 590
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-07-14 16:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 4:19 [PATCH V2 0/2] Drop the IPQ5019 SoC ID Kathiravan T
2023-07-12 4:19 ` [PATCH V2 1/2] dt-bindings: arm: qcom,ids: drop " Kathiravan T
2023-07-14 15:59 ` Rob Herring [this message]
2023-07-15 15:11 ` Kathiravan T
2023-07-22 4:02 ` Bjorn Andersson
2023-07-23 13:33 ` Kathiravan T
2023-07-12 4:19 ` [PATCH V2 2/2] soc: qcom: socinfo: " Kathiravan T
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=20230714155954.GA3919199-robh@kernel.org \
--to=robh@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.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_kathirav@quicinc.com \
--cc=quic_saahtoma@quicinc.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;
as well as URLs for NNTP newsgroup(s).