From: Ajay Kumar Nandam <ajay.nandam@oss.qualcomm.com>
To: Mark Brown <broonie@kernel.org>,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.com,
srini@kernel.org, linux-sound@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/3] ASoC: qcom: lpass: Switch VA/WSA macros to PM clock framework
Date: Tue, 23 Jun 2026 17:27:20 +0530 [thread overview]
Message-ID: <103ebcbe-685f-48e4-bf5a-4a0625e03a05@oss.qualcomm.com> (raw)
In-Reply-To: <7c4c3a7a-ad8f-4603-a0ec-2332f296234b@sirena.org.uk>
On 6/23/2026 4:55 PM, Mark Brown wrote:
>> On 6/23/26 9:17 AM, Ajay Kumar Nandam wrote:
>>> Hi,
>>>
>>> This series converts LPASS WSA and VA macro codec drivers to the PM clock
>>> framework for runtime PM clock handling, and keeps WSA MCLK-output clock
>>> registration resource-managed.
>>>
>>> Changes since v5:
>>> - Rebased to current linux-next/master and regenerated as a standalone
>>> series that applies cleanly.
>> Switch to using the b4 tool (https://b4.docs.kernel.org/). You sent
>> all messages as a separate thread.
> Also you already appear to have sent a v6 of this:
I did attempt to resend this series, but it seems I missed adding the
RESEND tag and ended up breaking the threading—apologies for the confusion.
You’re right, there is already a v6 posted earlier. I will ensure proper
versioning and threading going forward, and will use the b4 tool for
future submissions as suggested.
Ajay Kumar Nandam
>
> https://lore.kernel.org/all/20260604124823.3467457-1-
> ajay.nandam@oss.qualcomm.com/
next prev parent reply other threads:[~2026-06-23 11:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 7:17 Ajay Kumar Nandam
2026-06-23 10:29 ` Konrad Dybcio
2026-06-23 11:25 ` Mark Brown
2026-06-23 11:57 ` Ajay Kumar Nandam [this message]
2026-06-23 11:54 ` Ajay Kumar Nandam
-- strict thread matches above, loose matches on Subject: below --
2026-06-04 12:48 Ajay Kumar Nandam
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=103ebcbe-685f-48e4-bf5a-4a0625e03a05@oss.qualcomm.com \
--to=ajay.nandam@oss.qualcomm.com \
--cc=broonie@kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=srini@kernel.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