From: Stephen Boyd <sboyd@kernel.org>
To: Jernej Skrabec <jernej@kernel.org>, mturquette@baylibre.com
Cc: wens@csie.org, samuel@sholland.org, linux-clk@vger.kernel.org,
linux-sunxi@lists.linux.dev
Subject: Re: [GIT PULL] Allwinner clock fixes for 5.19
Date: Tue, 26 Jul 2022 10:56:17 -0700 [thread overview]
Message-ID: <20220726175619.4C627C433D6@smtp.kernel.org> (raw)
In-Reply-To: <YtnDy29glGFDhqU1@kista.localdomain>
Quoting Jernej Skrabec (2022-07-21 14:23:23)
> 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
Anymore details besides "Fix"? There's some more details in this pull
request but the tag tells me almost nothing. Does RTC fail? What's
actually broken?
prev parent reply other threads:[~2022-07-26 17:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 21:23 [GIT PULL] Allwinner clock fixes for 5.19 Jernej Skrabec
2022-07-26 17:56 ` Stephen Boyd [this message]
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=20220726175619.4C627C433D6@smtp.kernel.org \
--to=sboyd@kernel.org \
--cc=jernej@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=mturquette@baylibre.com \
--cc=samuel@sholland.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