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, 3 Apr 2022 07:09:59 -0700 [thread overview]
Message-ID: <20220403140959.113778-1-sboyd@kernel.org> (raw)
The following changes since commit cf683abd3913d5e6e51169de75d65ea193452fbd:
Merge branches 'clk-sifive' and 'clk-visconti' into clk-next (2022-03-29 10:19:52 -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 859c2c7b1d0623a6f523f970043db85ce0e5aa60:
Revert "clk: Drop the rate range on clk_put()" (2022-04-02 19:28:53 -0700)
----------------------------------------------------------------
A single revert to fix a boot regression seen when clk_put() started
dropping rate range requests. It's best to keep various systems booting
so we'll kick this out and try again next time.
----------------------------------------------------------------
Stephen Boyd (1):
Revert "clk: Drop the rate range on clk_put()"
drivers/clk/clk.c | 42 +++++++------------
drivers/clk/clk_test.c | 108 -------------------------------------------------
2 files changed, 14 insertions(+), 136 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:[~2022-04-03 14:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-03 14:09 Stephen Boyd [this message]
2022-04-03 20:29 ` [GIT PULL] one more clk change for the merge window pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2026-04-26 17:37 [GIT PULL] One " Stephen Boyd
2026-04-26 21:08 ` pr-tracker-bot
2019-05-16 23:04 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=20220403140959.113778-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 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.