From: Ajay Kumar Nandam <ajay.nandam@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
broonie@kernel.org, lgirdwood@gmail.com, perex@perex.cz,
tiwai@suse.com, srini@kernel.org
Cc: 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:24:06 +0530 [thread overview]
Message-ID: <7ac3fd70-e628-4fa2-a681-542aa18e692f@oss.qualcomm.com> (raw)
In-Reply-To: <7dccd968-6a58-4dd4-8ef8-5aa3f8591bf3@oss.qualcomm.com>
On 6/23/2026 3:59 PM, Konrad Dybcio 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.
>
ACK, thanks for pointing this out. I will use the b4 tool for the next
patch series to ensure proper threading.
I attempted to resend this series but ended up breaking the
thread—apologies for the confusion.
Ajay Kumar Nandam
> Konrad
next prev parent reply other threads:[~2026-06-23 11:54 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
2026-06-23 11:54 ` Ajay Kumar Nandam [this message]
-- 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=7ac3fd70-e628-4fa2-a681-542aa18e692f@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