From: patchwork-bot+linux-arm-msm@kernel.org
To: Srinivasa Rao Mandadapu <srivasam@codeaurora.org>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v6 0/2] Platform driver update to support playback recover after resume
Date: Mon, 01 Mar 2021 19:59:43 +0000 [thread overview]
Message-ID: <161462878307.6187.8991698056133795742.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1608192514-29695-1-git-send-email-srivasam@codeaurora.org>
Hello:
This series was applied to qcom/linux.git (refs/heads/for-next):
On Thu, 17 Dec 2020 13:38:32 +0530 you 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
>
> [...]
Here is the summary with links:
- [v6,1/2] ASoC: qcom: Fix incorrect volatile registers
https://git.kernel.org/qcom/c/315fbe4cef98
- [v6,2/2] ASoC: qcom: Add support for playback recover after resume
https://git.kernel.org/qcom/c/8d1bfc04c974
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-03-01 20:46 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 ` [PATCH v6 0/2] Platform driver update to support " Mark Brown
2021-03-01 19:59 ` patchwork-bot+linux-arm-msm [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=161462878307.6187.8991698056133795742.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-arm-msm@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=srivasam@codeaurora.org \
/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