From: Srinivasa Rao Mandadapu <quic_srivasam@quicinc.com>
To: Vinod Koul <vkoul@kernel.org>
Cc: <agross@kernel.org>, <bjorn.andersson@linaro.org>,
<lgirdwood@gmail.com>, <broonie@kernel.org>, <robh+dt@kernel.org>,
<quic_plai@quicinc.com>, <bgoswami@quicinc.com>, <perex@perex.cz>,
<tiwai@suse.com>, <srinivas.kandagatla@linaro.org>,
<quic_rohkumar@quicinc.com>, <linux-arm-msm@vger.kernel.org>,
<alsa-devel@alsa-project.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <swboyd@chromium.org>,
<judyhsiao@chromium.org>
Subject: Re: [PATCH v5 0/2] Add software clock gating requirement check
Date: Mon, 27 Jun 2022 18:01:38 +0530 [thread overview]
Message-ID: <7b532c96-e36b-207e-532c-8b41f7106831@quicinc.com> (raw)
In-Reply-To: <YrQfs7HUIOV5x8Ub@matsya>
On 6/23/2022 1:39 PM, Vinod Koul wrote:
Thanks for your time Vinod!!!
> On 10-06-22, 17:53, Srinivasa Rao Mandadapu wrote:
>> This patch set is to add software clock gating requirement check
> This fails to apply for me, please rebase on sdw-next and resend
>
> Thanks
It seems one patch is missing in your branch, which accepted by Mark brown.
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git/commit/?id=32882881078bd8f8fae47ff69c102d9e691f5bb9
next prev parent reply other threads:[~2022-06-27 12:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 12:23 [PATCH v5 0/2] Add software clock gating requirement check Srinivasa Rao Mandadapu
2022-06-10 12:23 ` [PATCH v5 1/2] soundwire: qcom: Add flag for software clock gating check Srinivasa Rao Mandadapu
2022-06-10 12:23 ` [PATCH v5 2/2] ASoC: qcom: soundwire: Enable software clock gating requirement flag Srinivasa Rao Mandadapu
2022-06-23 8:09 ` [PATCH v5 0/2] Add software clock gating requirement check Vinod Koul
2022-06-27 12:31 ` Srinivasa Rao Mandadapu [this message]
2022-06-29 5:00 ` Vinod Koul
2022-06-29 5:03 ` Srinivasa Rao Mandadapu
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=7b532c96-e36b-207e-532c-8b41f7106831@quicinc.com \
--to=quic_srivasam@quicinc.com \
--cc=agross@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bgoswami@quicinc.com \
--cc=bjorn.andersson@linaro.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=judyhsiao@chromium.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=quic_plai@quicinc.com \
--cc=quic_rohkumar@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=swboyd@chromium.org \
--cc=tiwai@suse.com \
--cc=vkoul@kernel.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