From: Stephen Boyd <sboyd@kernel.org>
To: Conor Dooley <conor@kernel.org>
Cc: conor@kernel.org, linux-riscv@lists.infradead.org,
linux-clk@vger.kernel.org, emil.renner.berthing@canonical.com,
xingyu.wu@starfivetech.com, walker.chen@starfivetech.com,
hal.feng@starfivetech.com
Subject: Re: [GIT PULL] StarFive clock driver additions for v6.6
Date: Wed, 19 Jul 2023 12:37:56 -0700 [thread overview]
Message-ID: <7d208aae212aa2101e8a9ca998a6a355.sboyd@kernel.org> (raw)
In-Reply-To: <20230719-trough-frisk-40b92acb485a@spud>
Quoting Conor Dooley (2023-07-19 10:37:55)
> Hey Stephen,
>
> Please pull some clock driver additions for StarFive. I've had these
> commits, other than a rebase to pick up R-b tags from Emil, out for LKP
> to have a look at for a few days and they've gotten a clean bill of
> health. Some of the dt-binding stuff "only" has a review from me, but
> since I am a dt-binding maintainer that's fine, although maybe not
> common knowledge yet.
>
> I've also gone and re-arranged the patches in this PR relative to their
> mailing list postings, so that the dt-binding patches can be used as a
> base for adding the clock controller nodes & dependant peripherals to
> the jh7110's dts.
>
> I'm hoping that next time around, someone from StarFive can send you the
> PR, maybe Walker, Hal or Xingyu are interested in that.
>
> Thanks,
> Conor.
>
> The following changes since commit 06c2afb862f9da8dc5efa4b6076a0e48c3fbaaa5:
>
> Linux 6.5-rc1 (2023-07-09 13:53:13 -0700)
>
> are available in the Git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux.git/ tags/clk-starfive-for-6.6
>
> for you to fetch changes up to dae5448a327edef952faaf31bb3aedb0597ba62a:
>
> clk: starfive: Add StarFive JH7110 Video-Output clock driver (2023-07-19 18:08:05 +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-07-19 19:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 17:37 [GIT PULL] StarFive clock driver additions for v6.6 Conor Dooley
2023-07-19 19:37 ` 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=7d208aae212aa2101e8a9ca998a6a355.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=walker.chen@starfivetech.com \
--cc=xingyu.wu@starfivetech.com \
/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).