From: Mark Brown <broonie@kernel.org>
To: robh+dt@kernel.org, Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
bgoswami@codeaurora.org, lgirdwood@gmail.com, sboyd@kernel.org,
plai@codeaurora.org, linux-kernel@vger.kernel.org,
tiwai@suse.com
Subject: Re: [PATCH 0/2] ASoC: q6afe: add clocks support
Date: Thu, 17 Sep 2020 19:57:10 +0100 [thread overview]
Message-ID: <160036900935.20113.3270260230921504372.b4-ty@kernel.org> (raw)
In-Reply-To: <20200910135708.14842-1-srinivas.kandagatla@linaro.org>
On Thu, 10 Sep 2020 14:57:06 +0100, Srinivas Kandagatla wrote:
> q6afe already exposes clocks using apis, but not as proper
> clock controller driver. This patch puts those clocks
> in to a proper clock controller so that other drivers that
> depend on those clocks can be properly expressed.
>
>
> Srinivas Kandagatla (2):
> ASoC: q6afe: dt-bindings: add q6afe clock bindings
> ASoC: q6afe-clocks: add q6afe clock controller
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/2] ASoC: q6afe: dt-bindings: add q6afe clock bindings
commit: 4e398353a7e51410c34fd19f8b7dfc56fff5901b
[2/2] ASoC: q6afe-clocks: add q6afe clock controller
commit: 520a1c396d1966b64884d8e0176a580150d5a09e
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
prev parent reply other threads:[~2020-09-17 19:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 13:57 [PATCH 0/2] ASoC: q6afe: add clocks support Srinivas Kandagatla
2020-09-10 13:57 ` [PATCH 1/2] ASoC: q6afe: dt-bindings: add q6afe clock bindings Srinivas Kandagatla
2020-09-10 13:57 ` [PATCH 2/2] ASoC: q6afe-clocks: add q6afe clock controller Srinivas Kandagatla
2020-09-17 18:57 ` Mark Brown [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=160036900935.20113.3270260230921504372.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bgoswami@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=plai@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=srinivas.kandagatla@linaro.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;
as well as URLs for NNTP newsgroup(s).