Linux clock framework development
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: mturquette@baylibre.com, Stephen Boyd <sboyd@kernel.org>
Cc: linux-clk@vger.kernel.org, linux-rockchip@lists.infradead.org
Subject: [GIT PULL] Rockchip clock changes for 6.13 #1
Date: Thu, 14 Nov 2024 23:38:35 +0100	[thread overview]
Message-ID: <3061836.mvXUDI8C0e@phil> (raw)

Hi Mike, Stephen,

please find below a pull-request with one Rockchip clock change for 6.13

Please pull.

Thanks
Heiko


The following changes since commit 9852d85ec9d492ebef56dc5f229416c925758edc:

  Linux 6.12-rc1 (2024-09-29 15:06:19 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v6.13-rockchip-clk1

for you to fetch changes up to 5011cc7ad9aeea98029385f8a0e81a0ebfc45bed:

  dt-bindings: clock: convert rockchip,rk3328-cru.txt to YAML (2024-10-08 21:11:29 +0200)

----------------------------------------------------------------
YAML conversion of the rk3328 clock controller binding.

----------------------------------------------------------------
Johan Jonker (1):
      dt-bindings: clock: convert rockchip,rk3328-cru.txt to YAML

 .../bindings/clock/rockchip,rk3328-cru.txt         | 58 -----------------
 .../bindings/clock/rockchip,rk3328-cru.yaml        | 74 ++++++++++++++++++++++
 2 files changed, 74 insertions(+), 58 deletions(-)
 delete mode 100644 Documentation/devicetree/bindings/clock/rockchip,rk3328-cru.txt
 create mode 100644 Documentation/devicetree/bindings/clock/rockchip,rk3328-cru.yaml




             reply	other threads:[~2024-11-14 22:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-14 22:38 Heiko Stuebner [this message]
2024-11-14 22:41 ` [GIT PULL] Rockchip clock changes for 6.13 #1 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=3061836.mvXUDI8C0e@phil \
    --to=heiko@sntech.de \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@kernel.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