From: Mark Brown <broonie@kernel.org>
To: robh@kernel.org,
Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>
Cc: krzk+dt@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, perex@perex.cz, tiwai@suse.com,
srini@kernel.org, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
alexey.klimov@linaro.org, konradybcio@kernel.org
Subject: Re: [PATCH v3 0/6] ASoC: codecs: lpass-macro: complete sm6115 support
Date: Fri, 14 Nov 2025 17:06:42 +0000 [thread overview]
Message-ID: <176314000202.179998.8192520322222862009.b4-ty@kernel.org> (raw)
In-Reply-To: <20251031120703.590201-1-srinivas.kandagatla@oss.qualcomm.com>
On Fri, 31 Oct 2025 12:06:57 +0000, Srinivas Kandagatla wrote:
> This patch series fixes SM6115 lpass codec macro support and adding
> missing dt-bindings to complete support for SM6115.
>
> SM6115 lpass codec macro support is added partially and broken to some
> extent, Fix this broken support and add complete lpass macro support for
> this SoC.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/6] ASoC: codecs: lpass-tx-macro: fix SM6115 support
commit: 7c63b5a8ed972a2c8c03d984f6a43349007cea93
[2/6] ASoC: dt-bindings: qcom,lpass-rx-macro: Add sm6115 LPASS RX
commit: 65d03e84d8b8e42cf4636fcabb81c9b130cec710
[3/6] ASoC: dt-bindings: qcom,lpass-va-macro: re-arrange clock-names
commit: 5a0438622b49df1e723960ac9c0bf75e04370fdc
[4/6] ASoC: dt-bindings: qcom,lpass-va-macro: Add sm6115 LPASS VA
commit: 675f41b8d1675d9a51a6dcb978ff76b95cbb4b92
[5/6] ASoC: codecs: lpass-va-macro: add SM6115 compatible
commit: 893e2fd509e968cc1d76caadee0f5d2f2c72f137
[6/6] ASoC: codecs: lpass-rx-macro: add SM6115 compatible
commit: 8ff3dcb0e8a8bf6c41f23ed4aa62d066d3948a10
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
prev parent reply other threads:[~2025-11-14 17:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 12:06 [PATCH v3 0/6] ASoC: codecs: lpass-macro: complete sm6115 support Srinivas Kandagatla
2025-10-31 12:06 ` [PATCH v3 1/6] ASoC: codecs: lpass-tx-macro: fix SM6115 support Srinivas Kandagatla
2025-10-31 12:06 ` [PATCH v3 2/6] ASoC: dt-bindings: qcom,lpass-rx-macro: Add sm6115 LPASS RX Srinivas Kandagatla
2025-11-02 16:21 ` Krzysztof Kozlowski
2025-10-31 12:07 ` [PATCH v3 3/6] ASoC: dt-bindings: qcom,lpass-va-macro: re-arrange clock-names Srinivas Kandagatla
2025-11-02 16:24 ` Krzysztof Kozlowski
2025-10-31 12:07 ` [PATCH v3 4/6] ASoC: dt-bindings: qcom,lpass-va-macro: Add sm6115 LPASS VA Srinivas Kandagatla
2025-11-02 16:24 ` Krzysztof Kozlowski
2025-10-31 12:07 ` [PATCH v3 5/6] ASoC: codecs: lpass-va-macro: add SM6115 compatible Srinivas Kandagatla
2025-10-31 12:07 ` [PATCH v3 6/6] ASoC: codecs: lpass-rx-macro: " Srinivas Kandagatla
2025-10-31 14:46 ` [PATCH v3 0/6] ASoC: codecs: lpass-macro: complete sm6115 support Dmitry Baryshkov
2025-10-31 14:51 ` Srinivas Kandagatla
2025-11-14 17:06 ` Mark Brown [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=176314000202.179998.8192520322222862009.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alexey.klimov@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=robh@kernel.org \
--cc=srini@kernel.org \
--cc=srinivas.kandagatla@oss.qualcomm.com \
--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