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] One more clk change for the merge window
Date: Sun, 26 Apr 2026 10:37:29 -0700 [thread overview]
Message-ID: <20260426173730.2296370-1-sboyd@kernel.org> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]
The following changes since commit 6b701fde9b31f085f39fc2a371cb33212fab6f68:
Merge branches 'clk-samsung', 'clk-qcom', 'clk-round', 'clk-sai' and 'clk-cleanup' into clk-next (2026-04-16 10:12:43 -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 522567362b634015ca85b5460482ee0843feb105:
clk: bcm: rpi: Mark VEC clock as CLK_IGNORE_UNUSED (2026-04-25 10:51:23 -0700)
----------------------------------------------------------------
One more fix for the merge window to avoid a boot hang on
Raspberry Pi 3B by marking the VEC clk critical so it doesn't get
turned off and hang the bus.
----------------------------------------------------------------
Maíra Canal (1):
clk: bcm: rpi: Mark VEC clock as CLK_IGNORE_UNUSED
drivers/clk/bcm/clk-raspberrypi.c | 7 +++++++
1 file changed, 7 insertions(+)
--
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:[~2026-04-26 17:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-26 17:37 Stephen Boyd [this message]
2026-04-26 21:08 ` [GIT PULL] One more clk change for the merge window pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2022-04-03 14:09 [GIT PULL] one " Stephen Boyd
2022-04-03 20:29 ` pr-tracker-bot
2019-05-16 23:04 [GIT PULL] One " Stephen Boyd
2019-05-17 2:25 ` pr-tracker-bot
2019-01-02 17:53 [GIT PULL] one " Stephen Boyd
2019-01-03 3:05 ` 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=20260426173730.2296370-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