From: Vinod Koul <vkoul@kernel.org>
To: Vijendar Mukunda <Vijendar.Mukunda@amd.com>
Cc: yung-chuan.liao@linux.intel.com, pierre-louis.bossart@linux.dev,
sanyog.r.kale@intel.com, Basavaraj.Hiregoudar@amd.com,
Sunil-kumar.Dommati@amd.com, venkataprasad.potturu@amd.com,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] soundwire: amd: fixes and improvements
Date: Mon, 09 Jun 2025 21:47:01 +0530 [thread overview]
Message-ID: <174948582129.818066.6657082052541545420.b4-ty@kernel.org> (raw)
In-Reply-To: <20250530054447.1645807-1-Vijendar.Mukunda@amd.com>
On Fri, 30 May 2025 11:13:38 +0530, Vijendar Mukunda wrote:
> This patch series consists of fixes and improvements for
> AMD Soundwire stack.
>
> Vijendar Mukunda (3):
> soundwire: amd: fix for handling slave alerts after link is down
> soundwire: amd: serialize amd manager resume sequence during
> pm_prepare
> soundwire: amd: cancel pending slave status handling workqueue during
> remove sequence
>
> [...]
Applied, thanks!
[1/3] soundwire: amd: fix for handling slave alerts after link is down
commit: 86a4371b76976158be875dc654ceee35c574b27b
[2/3] soundwire: amd: serialize amd manager resume sequence during pm_prepare
(no commit info)
[3/3] soundwire: amd: cancel pending slave status handling workqueue during remove sequence
(no commit info)
Best regards,
--
~Vinod
prev parent reply other threads:[~2025-06-09 16:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-30 5:43 Vijendar Mukunda
2025-05-30 5:43 ` [PATCH 1/3] soundwire: amd: fix for handling slave alerts after link is down Vijendar Mukunda
2025-05-30 5:43 ` [PATCH 2/3] soundwire: amd: serialize amd manager resume sequence during pm_prepare Vijendar Mukunda
2025-05-30 5:43 ` [PATCH 3/3] soundwire: amd: cancel pending slave status handling workqueue during remove sequence Vijendar Mukunda
2025-06-07 0:06 ` [PATCH 0/3] soundwire: amd: fixes and improvements Mukunda,Vijendar
2025-06-09 16:17 ` Vinod Koul [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=174948582129.818066.6657082052541545420.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=Basavaraj.Hiregoudar@amd.com \
--cc=Sunil-kumar.Dommati@amd.com \
--cc=Vijendar.Mukunda@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=pierre-louis.bossart@linux.dev \
--cc=sanyog.r.kale@intel.com \
--cc=venkataprasad.potturu@amd.com \
--cc=yung-chuan.liao@linux.intel.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®