From: Stephen Boyd <sboyd@kernel.org>
To: Conor Dooley <conor@kernel.org>, p.zabel@pengutronix.de
Cc: linux-clk@vger.kernel.org, linux-riscv@lists.infradead.org,
hal.feng@starfivetech.com, emil.renner.berthing@canonical.com,
conor@kernel.org, mturquette@baylibre.com
Subject: Re: [GIT PULL] Initial clk/reset support for JH7110 for v6.4
Date: Wed, 05 Apr 2023 11:56:22 -0700 [thread overview]
Message-ID: <85648045b35c889f61a536cdd568b867.sboyd@kernel.org> (raw)
In-Reply-To: <20230405-constant-dreamily-0128e071c665@spud>
Quoting Conor Dooley (2023-04-05 09:05:01)
> Hey Stephen, (and Philipp if you want I guess?),
>
> Here's a PR for the StarFive JH7110 clk/reset bits since I'd like to
> take the DT this cycle & depend on the binding headers.
>
> I've picked up R-B tags from Emil on all that patches, despite him being
> listed as an author, as things have changed quite a lot since he was
> involved in writing things many months ago.
>
> The base here is -rc2 rather than -rc1 as -rc1 has issues booting on
> this platform. Please pull and all that lark..
>
> Cheers,
> Conor.
>
> The following changes since commit eeac8ede17557680855031c6f305ece2378af326:
>
> Linux 6.3-rc2 (2023-03-12 16:36:44 -0700)
>
> are available in the Git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux.git/ tags/riscv-jh7110-clk-reset-for-6.4
>
> for you to fetch changes up to 63a30e1f44d5e3afbb47efe8a15fd86feeb62b4b:
>
> MAINTAINERS: generalise StarFive clk/reset entries (2023-04-05 15:52:25 +0100)
>
> ----------------------------------------------------------------
Thanks. Pulled into clk-next
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2023-04-05 18:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 16:05 [GIT PULL] Initial clk/reset support for JH7110 for v6.4 Conor Dooley
2023-04-05 18: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=85648045b35c889f61a536cdd568b867.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=conor@kernel.org \
--cc=emil.renner.berthing@canonical.com \
--cc=hal.feng@starfivetech.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
/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).