From: Stephen Boyd <sboyd@kernel.org>
To: "Jernej Škrabec" <jernej.skrabec@gmail.com>,
"Samuel Holland" <samuel@sholland.org>,
wens@csie.org
Cc: mturquette@baylibre.com, andre.przywara@arm.com,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: sunxi-ng: Fix H6 RTC clock definition
Date: Tue, 26 Jul 2022 15:58:53 -0700 [thread overview]
Message-ID: <20220726225855.615E1C433D6@smtp.kernel.org> (raw)
In-Reply-To: <2118699.Icojqenx9y@jernej-laptop>
Quoting Jernej Škrabec (2022-07-20 08:16:54)
> Dne sreda, 20. julij 2022 ob 02:21:29 CEST je Samuel Holland napisal(a):
> > On 7/19/22 1:37 PM, Jernej Skrabec wrote:
> > >
> > > Fixes: 38d321b61bda ("clk: sunxi-ng: h6-r: Add RTC gate clock")
> > > Signed-off-by: Jernej Skrabec <jernej.skrabec@gmail.com>
> >
> > Reviewed-by: Samuel Holland <samuel@sholland.org>
> >
> > This bug also got fixed in passing by e1c51d31befc ("clk: sunxi-ng:
> > Deduplicate ccu_clks arrays"), but that won't land until 5.20.
>
> Argh, good catch. I will send your patch as fix then, otherwise there will be
> issues during merging.
This is a one line fix. I can just apply this and send this off and deal
with the merge conflict locally by taking the other side.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-07-26 23:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 18:37 [PATCH] clk: sunxi-ng: Fix H6 RTC clock definition Jernej Skrabec
2022-07-20 0:21 ` Samuel Holland
2022-07-20 15:16 ` Jernej Škrabec
2022-07-26 22:58 ` Stephen Boyd [this message]
2022-07-27 2:26 ` Samuel Holland
2022-07-27 23:47 ` 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=20220726225855.615E1C433D6@smtp.kernel.org \
--to=sboyd@kernel.org \
--cc=andre.przywara@arm.com \
--cc=jernej.skrabec@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).