From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: lgirdwood@gmail.com, bjorn.andersson@linaro.org, perex@perex.cz,
tiwai@suse.com, srinivas.kandagatla@linaro.org,
robh+dt@kernel.org, krzk+dt@kernel.org,
alsa-devel@alsa-project.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v4 1/2] ASoC: qcom: lpass: Fix apq8016 compat string to match yaml
Date: Tue, 28 Jun 2022 12:48:20 +0100 [thread overview]
Message-ID: <14f6b7eb-cacb-91a5-ce06-9702618513b9@linaro.org> (raw)
In-Reply-To: <Yrrf5X8wstW+DXHF@sirena.org.uk>
On 28/06/2022 12:03, Mark Brown wrote:
> On Tue, Jun 28, 2022 at 01:28:57AM +0100, Bryan O'Donoghue wrote:
>> The documented yaml compat string for the apq8016 is
>> "qcom,apq8016-lpass-cpu" not "qcom,lpass-cpu-apq8016". Looking at the other
>> lpass compat strings the general form is "qcom,socnum-lpass-cpu".
>
> This doesn't apply against current code, please check and resend.
What's the tree you are applying to here ?
I applied it to linux-next just last night..
https://git.linaro.org/people/bryan.odonoghue/kernel.git/log/?h=linux-next-27-06-22-msm8939-no-cpr-v4
https://git.linaro.org/people/bryan.odonoghue/kernel.git/commit/?h=linux-next-27-06-22-msm8939-no-cpr-v4&id=5822d52637eff65b826097634d9a99a9bf1bf2b7
---
bod
next prev parent reply other threads:[~2022-06-28 11:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 0:28 [PATCH v4 0/2] Fix apq8016 compat string Bryan O'Donoghue
2022-06-28 0:28 ` [PATCH v4 1/2] ASoC: qcom: lpass: Fix apq8016 compat string to match yaml Bryan O'Donoghue
2022-06-28 10:54 ` Mark Brown
2022-06-28 11:03 ` Mark Brown
2022-06-28 11:48 ` Bryan O'Donoghue [this message]
2022-06-28 12:07 ` Mark Brown
2022-06-28 13:25 ` Bryan O'Donoghue
2022-06-28 0:28 ` [PATCH v4 2/2] arm64: dts: qcom: " Bryan O'Donoghue
2022-06-28 13:25 ` (subset) [PATCH v4 0/2] Fix apq8016 compat string Mark Brown
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=14f6b7eb-cacb-91a5-ce06-9702618513b9@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=alsa-devel@alsa-project.org \
--cc=bjorn.andersson@linaro.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=perex@perex.cz \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=tiwai@suse.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).