Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Parikshit Pareek <quic_ppareek@quicinc.com>
Cc: Andy Gross <agross@kernel.org>,
	Sai Prakash Ranjan <quic_saipraka@quicinc.com>,
	Rajendra Nayak <quic_rjendra@quicinc.com>,
	Prasanna Kumar <quic_kprasan@quicinc.com>,
	linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v4] soc: qcom: Fix the id of SA8540P SoC
Date: Sat, 16 Jul 2022 10:09:41 -0500	[thread overview]
Message-ID: <YtLUtTY7iui5EtXz@builder.lan> (raw)
In-Reply-To: <20220711083957.12091-1-quic_ppareek@quicinc.com>

On Mon 11 Jul 03:39 CDT 2022, Parikshit Pareek wrote:

> Change the id of SA8540P to its correct value, i.e., 461.
> Also, map the id 460 to its correct values, i.e. SA8295P.
> 
> Fixes: 76ee15ae1b13 ("soc: qcom: socinfo: Add some more PMICs and SoCs")
> Signed-off-by: Parikshit Pareek <quic_ppareek@quicinc.com>
> Reviewed-by: Eric Chanudet <echanude@redhat.com>
> Tested-by: Eric Chanudet <echanude@redhat.com>

Thanks for the fix and welcome to the upstream kernel!

I added "socinfo:" to the subject prefix and applied the change.

Regards,
Bjorn

> ---
>  drivers/soc/qcom/socinfo.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/soc/qcom/socinfo.c b/drivers/soc/qcom/socinfo.c
> index c2c879ccc6c0..4554fb8655d3 100644
> --- a/drivers/soc/qcom/socinfo.c
> +++ b/drivers/soc/qcom/socinfo.c
> @@ -328,7 +328,8 @@ static const struct soc_id soc_id[] = {
>  	{ 455, "QRB5165" },
>  	{ 457, "SM8450" },
>  	{ 459, "SM7225" },
> -	{ 460, "SA8540P" },
> +	{ 460, "SA8295P" },
> +	{ 461, "SA8540P" },
>  	{ 480, "SM8450" },
>  	{ 482, "SM8450" },
>  	{ 487, "SC7280" },
> -- 
> 2.17.1
> 

  reply	other threads:[~2022-07-16 15:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11  8:39 [PATCH v4] soc: qcom: Fix the id of SA8540P SoC Parikshit Pareek
2022-07-16 15:09 ` Bjorn Andersson [this message]
2022-07-16 15:19 ` (subset) " Bjorn Andersson

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=YtLUtTY7iui5EtXz@builder.lan \
    --to=bjorn.andersson@linaro.org \
    --cc=agross@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=quic_kprasan@quicinc.com \
    --cc=quic_ppareek@quicinc.com \
    --cc=quic_rjendra@quicinc.com \
    --cc=quic_saipraka@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