From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>, broonie@kernel.org
Cc: lgirdwood@gmail.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, bgoswami@quicinc.com,
perex@perex.cz, tiwai@suse.com, linux-arm-msm@vger.kernel.org,
alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/4] ASoC: qcom: sm8250: move some code to common
Date: Thu, 8 Sep 2022 15:26:39 +0200 [thread overview]
Message-ID: <6cc3a526-8ff8-8000-d406-c4d8949c6f68@linaro.org> (raw)
In-Reply-To: <20220906165508.30801-4-srinivas.kandagatla@linaro.org>
On 06/09/2022 18:55, Srinivas Kandagatla wrote:
> SM8450 machine driver code can be reused across multiple Qualcomm SoCs,
> atleast another 2 of them for now (SM8450 and SM8250XP).
>
> Move some of the common SoundWire stream specific code to common file
> so that other drivers can use it instead of duplicating.
>
> This patch is to prepare the common driver to be able to add new SoCs support
> with less dupication.
>
> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
> ---
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-09-08 13:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 16:55 [PATCH v2 0/4] ASoC: qcom: add support for sc8280xp machine Srinivas Kandagatla
2022-09-06 16:55 ` [PATCH v2 1/4] ASoC: qcom: common: use EXPORT_SYMBOL_GPL instead of EXPORT_SYMBOL Srinivas Kandagatla
2022-09-08 13:22 ` Krzysztof Kozlowski
2022-09-06 16:55 ` [PATCH v2 2/4] ASoC: dt-bindings: qcom,sm8250: add compatibles for sm8450 and sm8250 Srinivas Kandagatla
2022-09-06 16:55 ` [PATCH v2 3/4] ASoC: qcom: sm8250: move some code to common Srinivas Kandagatla
2022-09-08 13:26 ` Krzysztof Kozlowski [this message]
2022-09-06 16:55 ` [PATCH v2 4/4] ASoC: qcom: add machine driver for sc8280xp Srinivas Kandagatla
2022-09-08 13:28 ` Krzysztof Kozlowski
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=6cc3a526-8ff8-8000-d406-c4d8949c6f68@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alsa-devel@alsa-project.org \
--cc=bgoswami@quicinc.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®