From: Mark Brown <broonie@kernel.org>
To: linux-arm-msm@vger.kernel.org, perex@perex.cz,
linux-kernel@vger.kernel.org, bgoswami@codeaurora.org,
tiwai@suse.com, lgirdwood@gmail.com, swboyd@chromium.org,
agross@kernel.org, judyhsiao@chromium.org,
alsa-devel@alsa-project.org, bjorn.andersson@linaro.org,
srinivas.kandagatla@linaro.org, devicetree@vger.kernel.org,
robh+dt@kernel.org,
Srinivasa Rao Mandadapu <quic_srivasam@quicinc.com>,
rohitkr@codeaurora.org, quic_plai@quicinc.com
Subject: Re: [PATCH v4 0/2] Add power domains support for digital macro codecs
Date: Mon, 28 Feb 2022 19:15:39 +0000 [thread overview]
Message-ID: <164607573904.3538791.16540077443386812939.b4-ty@kernel.org> (raw)
In-Reply-To: <1645786624-12311-1-git-send-email-quic_srivasam@quicinc.com>
On Fri, 25 Feb 2022 16:27:02 +0530, Srinivasa Rao Mandadapu wrote:
> This patch set is to add power domains support for RX, TX and VA macros.
>
> Changes since v3:
> -- Add dt-bindings support.
> Changes since v2:
> -- Remove redundant local variable.
> -- Update pds error handling sequence.
> -- Update module description.
> -- Clean up pds init function.
> -- Remove redundant arguments.
> Changes since v1:
> -- Add missing macros in Kconfig.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/2] ASoC: codecs: Add power domains support in digital macro codecs
commit: 9e3d83c52844f955aa2975f78cee48bf9f72f5e1
[2/2] ASoC: qcom: dt-bindings: Add bindings for power domains in lpass digital codecs
commit: 6619c7d4379aca716a90f7581be2853071c086f6
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:[~2022-02-28 19:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 10:57 Srinivasa Rao Mandadapu
2022-02-25 10:57 ` [PATCH v4 1/2] ASoC: codecs: Add power domains support in " Srinivasa Rao Mandadapu
2022-02-25 10:57 ` [PATCH v4 2/2] ASoC: qcom: dt-bindings: Add bindings for power domains in lpass digital codecs Srinivasa Rao Mandadapu
2022-02-25 17:36 ` [PATCH v4 0/2] Add power domains support for digital macro codecs Mark Brown
2022-02-28 19:15 ` 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=164607573904.3538791.16540077443386812939.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=agross@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bgoswami@codeaurora.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=judyhsiao@chromium.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=quic_plai@quicinc.com \
--cc=quic_srivasam@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=rohitkr@codeaurora.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=swboyd@chromium.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®