From: patchwork-bot+linux-arm-msm@kernel.org
To: Taniya Das <tdas@codeaurora.org>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v4 0/2] Add support for LPASS Core and Audio Clock for SC7280
Date: Wed, 13 Apr 2022 14:30:20 +0000 [thread overview]
Message-ID: <164986022057.5431.1494884054717989884.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220126081236.25255-1-tdas@codeaurora.org>
Hello:
This series was applied to qcom/linux.git (for-next)
by Bjorn Andersson <bjorn.andersson@linaro.org>:
On Wed, 26 Jan 2022 13:42:34 +0530 you wrote:
> [v4]
> * Cleanup header file inclusion in the clock controller files.
> * Update the regmap_config max_registers in all clock controller
> probes.
>
> [v3]
> * Fix 'pm_clk_suspend' expansion warning in lpass_audio_cc_sc7280_probe
> and lpass_aon_cc_sc7280_probe.
> * Update the vco table frequencies.
> * Update 'regmap_config' name for all clock controllers.
> * Fix the missing 'const' for clk_init_data.
> * Update the binding for 'lpass_aon' CC.
>
> [...]
Here is the summary with links:
- [v4,1/2] dt-bindings: clock: Add YAML schemas for LPASS clocks on SC7280
https://git.kernel.org/qcom/c/4185b27b3bef
- [v4,2/2] clk: qcom: lpass: Add support for LPASS clock controller for SC7280
(no matching commit)
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:[~2022-04-13 14:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 8:12 [PATCH v4 0/2] Add support for LPASS Core and Audio Clock for SC7280 Taniya Das
2022-01-26 8:12 ` [PATCH v4 1/2] dt-bindings: clock: Add YAML schemas for LPASS clocks on SC7280 Taniya Das
2022-02-04 23:17 ` Rob Herring
2022-02-17 22:40 ` Stephen Boyd
2022-01-26 8:12 ` [PATCH v4 2/2] clk: qcom: lpass: Add support for LPASS clock controller for SC7280 Taniya Das
2022-02-17 22:42 ` Stephen Boyd
2022-04-13 14:30 ` 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=164986022057.5431.1494884054717989884.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-arm-msm@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=tdas@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.