devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: srinivas.kandagatla@linaro.org, bjorn.andersson@linaro.org,
	robh+dt@kernel.org, krzk+dt@kernel.org
Cc: alsa-devel@alsa-project.org, linux-arm-msm@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v3 0/2] Fix apq8016 compat string
Date: Wed, 25 May 2022 14:02:29 +0100	[thread overview]
Message-ID: <78da8864-eb65-8dd5-cde5-0c0fc63b9ebf@linaro.org> (raw)
In-Reply-To: <20220429220349.1142759-1-bryan.odonoghue@linaro.org>

On 29/04/2022 23:03, Bryan O'Donoghue wrote:
> V3:
> - Marks qcom,lpass-cpu-apq8016 as deprecated instead of removing - Bjorn
> 
> V2:
> - Adds Reviewed-by: - Srini
> - Adds Fixes - Srini
> 
> V1:
> Reusing the apq8016 on msm8939 I found running checkpatch that the compat
> string for the LPASS was throwing a warning.
> 
> This is easily fixed by alinging the YAML, DTS and driver to the documented
> compat string
> 
> -			compatible = "qcom,lpass-cpu-apq8016";
> +			compatible = "qcom,apq8016-lpass-cpu";
> 
> 
> Bryan O'Donoghue (2):
>    ASoC: qcom: lpass: Fix apq8016 compat string to match yaml
>    arm64: dts: qcom: Fix apq8016 compat string to match yaml
> 
>   arch/arm64/boot/dts/qcom/msm8916.dtsi | 2 +-
>   sound/soc/qcom/lpass-apq8016.c        | 1 +
>   sound/soc/qcom/lpass-cpu.c            | 5 +++++
>   3 files changed, 7 insertions(+), 1 deletion(-)
> 
ping

      parent reply	other threads:[~2022-05-25 13:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-29 22:03 [PATCH v3 0/2] Fix apq8016 compat string Bryan O'Donoghue
2022-04-29 22:03 ` [PATCH v3 1/2] ASoC: qcom: lpass: Fix apq8016 compat string to match yaml Bryan O'Donoghue
2022-06-27 20:40   ` Bjorn Andersson
2022-06-27 22:24     ` Mark Brown
2022-04-29 22:03 ` [PATCH v3 2/2] arm64: dts: qcom: " Bryan O'Donoghue
2022-05-25 13:02 ` Bryan O'Donoghue [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=78da8864-eb65-8dd5-cde5-0c0fc63b9ebf@linaro.org \
    --to=bryan.odonoghue@linaro.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=srinivas.kandagatla@linaro.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).