From: Stephen Boyd <sboyd@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] clk fixes for the merge window
Date: Fri, 26 Jul 2024 11:57:14 -0700 [thread overview]
Message-ID: <20240726185715.3655728-1-sboyd@kernel.org> (raw)
The following changes since commit 589eb11498fbf7de7a1bc8ff1f4b7592687dfd46:
Merge branches 'clk-qcom', 'clk-rockchip', 'clk-sophgo' and 'clk-thead' into clk-next (2024-07-16 11:24:25 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git tags/clk-for-linus
for you to fetch changes up to f99b3feb3b0e9fca2257c90fc8317be8ee44c19a:
clk: samsung: fix getting Exynos4 fin_pll rate from external clocks (2024-07-23 11:29:23 -0700)
----------------------------------------------------------------
A few clk driver fixes for the merge window to fix the build and boot on
some SoCs.
- Initialize struct clk_init_data in the TI da8xx-cfgchip driver so
that stack contents aren't used for things like clk flags leading to
unexpected behavior
- Don't leak stack contents in a debug print in the new Sophgo clk
driver
- Disable the new T-Head clk driver on 32-bit targets to fix the build
due to a division
- Fix Samsung Exynos4 fin_pll wreckage from the clkdev rework done last
cycle by using a struct clk_hw directly instead of a struct clk
consumer
----------------------------------------------------------------
Bastien Curutchet (1):
clk: davinci: da8xx-cfgchip: Initialize clk_init_data before use
Dan Carpenter (1):
clk: sophgo: clk-sg2042-pll: Fix uninitialized variable in debug output
Krzysztof Kozlowski (1):
clk: samsung: fix getting Exynos4 fin_pll rate from external clocks
Palmer Dabbelt (1):
clk: T-Head: Disable on 32-bit Targets
drivers/clk/davinci/da8xx-cfgchip.c | 4 ++--
drivers/clk/samsung/clk-exynos4.c | 13 +++++++------
drivers/clk/sophgo/clk-sg2042-pll.c | 2 +-
drivers/clk/thead/Kconfig | 1 +
4 files changed, 11 insertions(+), 9 deletions(-)
--
https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git/
https://git.kernel.org/pub/scm/linux/kernel/git/sboyd/spmi.git
next reply other threads:[~2024-07-26 18:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-26 18:57 Stephen Boyd [this message]
2024-07-27 20:07 ` pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2022-01-20 20:56 Stephen Boyd
2022-01-21 7:38 ` pr-tracker-bot
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=20240726185715.3655728-1-sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=torvalds@linux-foundation.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
Powered by JetHome