From: Mark Brown <broonie@kernel.org>
To: alsa-devel@alsa-project.org, tiwai@suse.com,
Srinivasa Rao Mandadapu <srivasam@codeaurora.org>,
plai@codeaurora.org, devicetree@vger.kernel.org,
rohitkr@codeaurora.org, lgirdwood@gmail.com,
linux-kernel@vger.kernel.org, srinivas.kandagatla@linaro.org,
bjorn.andersson@linaro.org, agross@kernel.org,
robh+dt@kernel.org, linux-arm-msm@vger.kernel.org,
bgoswami@codeaurora.org, perex@perex.cz
Subject: Re: [PATCH v6 0/2] Platform driver update to support playback recover after resume
Date: Fri, 18 Dec 2020 12:16:10 +0000 [thread overview]
Message-ID: <160829377017.10885.961383820010560969.b4-ty@kernel.org> (raw)
In-Reply-To: <1608192514-29695-1-git-send-email-srivasam@codeaurora.org>
On Thu, 17 Dec 2020 13:38:32 +0530, Srinivasa Rao Mandadapu wrote:
> This patch set is to add support for playback recover after hard suspend and resume.
> It includes:
> 1. Reverting part of previous commit, which is for handling registers invalid state
> after hard suspend.
> 2. Adding pm ops in component driver and do regcache sync.
> Changes Since v1 and v2:
> -- Subject lines changed
> Changes Since v3:
> -- Patch is splitted into 2 patches
> Changes Since v4:
> -- Subject lines changed
> Changes Since v5:
> -- Removed redundant initialization of map variable in lpass-platform.c
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/2] ASoC: qcom: Fix incorrect volatile registers
commit: 315fbe4cef98ee5fb6085bc54c7f25eb06466c70
[2/2] ASoC: qcom: Add support for playback recover after resume
commit: 8d1bfc04c97407767559f6389a0f0fb060cbe25e
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
next prev parent reply other threads:[~2020-12-18 12:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 8:08 [PATCH v6 0/2] Platform driver update to support playback recover after resume Srinivasa Rao Mandadapu
2020-12-17 8:08 ` [PATCH v6 1/2] ASoC: qcom: Fix incorrect volatile registers Srinivasa Rao Mandadapu
2020-12-17 8:08 ` [PATCH v6 2/2] ASoC: qcom: Add support for playback recover after resume Srinivasa Rao Mandadapu
2020-12-18 12:16 ` Mark Brown [this message]
2021-03-01 19:59 ` [PATCH v6 0/2] Platform driver update to support " patchwork-bot+linux-arm-msm
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=160829377017.10885.961383820010560969.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=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=plai@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=rohitkr@codeaurora.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=srivasam@codeaurora.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