From: Jernej Skrabec <jernej@kernel.org>
To: mturquette@baylibre.com, sboyd@kernel.org
Cc: wens@csie.org, samuel@sholland.org, linux-clk@vger.kernel.org,
linux-sunxi@lists.linux.dev
Subject: [GIT PULL] Allwinner clock fixes for 5.19
Date: Thu, 21 Jul 2022 23:23:23 +0200 [thread overview]
Message-ID: <YtnDy29glGFDhqU1@kista.localdomain> (raw)
Hi!
As it turns out, commit 38d321b61bda ("clk: sunxi-ng: h6-r: Add RTC gate
clock"), queued for 5.19, introduced a bug. This bug is accidentally
fixed by commit e1c51d31befc ("clk: sunxi-ng: Deduplicate ccu_clks
arrays"), which is already queued for 5.20.
Although this commit as a fix is much bigger than it needs to be, I
still suggest that's fast tracked to 5.19. This will also avoid any
merge conflicts during merging material for 5.20.
Best regards,
Jernej
The following changes since commit f2906aa863381afb0015a9eb7fefad885d4e5a56:
Linux 5.19-rc1 (2022-06-05 17:18:54 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux.git tags/sunxi-clk-fixes-for-5.19-1
for you to fetch changes up to 48e29e0f3be086a28a9384befa77d02a43be2f98:
clk: sunxi-ng: Deduplicate ccu_clks arrays (2022-07-21 23:11:28 +0200)
----------------------------------------------------------------
Fix H6 RTC clock
----------------------------------------------------------------
Samuel Holland (1):
clk: sunxi-ng: Deduplicate ccu_clks arrays
drivers/clk/sunxi-ng/ccu-sun50i-h6-r.c | 16 +----
drivers/clk/sunxi-ng/ccu-sun8i-de2.c | 79 ++++++-----------------
drivers/clk/sunxi-ng/ccu-sun8i-h3.c | 113 +--------------------------------
drivers/clk/sunxi-ng/ccu-sun8i-r.c | 40 +++---------
drivers/clk/sunxi-ng/ccu-sun8i-v3s.c | 84 ++----------------------
5 files changed, 40 insertions(+), 292 deletions(-)
next reply other threads:[~2022-07-21 21:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 21:23 Jernej Skrabec [this message]
2022-07-26 17:56 ` [GIT PULL] Allwinner clock fixes for 5.19 Stephen Boyd
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=YtnDy29glGFDhqU1@kista.localdomain \
--to=jernej@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=mturquette@baylibre.com \
--cc=samuel@sholland.org \
--cc=sboyd@kernel.org \
--cc=wens@csie.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