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: Thu, 20 Jan 2022 12:56:37 -0800 [thread overview]
Message-ID: <20220120205637.2234852-1-sboyd@kernel.org> (raw)
The following changes since commit 4afd2a9355a9deb16ea42b896820dacf49843a8f:
Merge branches 'clk-ingenic' and 'clk-mediatek' into clk-next (2022-01-11 18:31:00 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git tags/clk-fixes-for-linus
for you to fetch changes up to b4966a7dc0725b2baa12b0aeb1489d52568a2aad:
clk: mediatek: relicense mt7986 clock driver to GPL-2.0 (2022-01-19 12:05:07 -0800)
----------------------------------------------------------------
Some hot fixes for clk driver patches merged last week
and one oops fix.
- Fix license on recent MediaTek drivers
- Initialize a variable before use in the new Visconti driver
- Avoid an oops by unregistering the clk provider in si5341
----------------------------------------------------------------
Dan Carpenter (1):
clk: visconti: Fix uninitialized variable in printk
Robert Hancock (1):
clk: si5341: Fix clock HW provider cleanup
Sam Shih (1):
clk: mediatek: relicense mt7986 clock driver to GPL-2.0
drivers/clk/clk-si5341.c | 2 +-
drivers/clk/mediatek/clk-mt7986-apmixed.c | 2 +-
drivers/clk/mediatek/clk-mt7986-infracfg.c | 2 +-
drivers/clk/mediatek/clk-mt7986-topckgen.c | 2 +-
drivers/clk/visconti/pll.c | 3 +--
5 files changed, 5 insertions(+), 6 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-01-20 20:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 20:56 Stephen Boyd [this message]
2022-01-21 7:38 ` [GIT PULL] clk fixes for the merge window 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=20220120205637.2234852-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;
as well as URLs for NNTP newsgroup(s).