From: "Heiko Stübner" <heiko@sntech.de>
To: arm@kernel.org
Cc: soc@kernel.org, linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] Rockchip dts32 changes for 6.13 #1 - please ignore
Date: Mon, 11 Nov 2024 16:36:00 +0100 [thread overview]
Message-ID: <3580458.V25eIC5XRa@diego> (raw)
In-Reply-To: <6740039.4vTCxPXJkl@diego>
Hi,
I messed up the subject, this was supposed to be #2
New one coming up in a minute.
Heiko
Am Montag, 11. November 2024, 16:35:03 CET schrieb Heiko Stuebner:
> The following changes since commit bdb2696ac5786ed3f43520e700347fe2152ea199:
>
> ARM: dts: rockchip: Add Relfor Saib board (2024-10-14 11:35:50 +0200)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v6.13-rockchip-dts32-2
>
> for you to fetch changes up to 2c3944d952ec4d3428a8d3163be2263579d1939a:
>
> ARM: dts: rockchip: adapt regulator nodenames to preferred form (2024-11-09 18:43:23 +0100)
>
> ----------------------------------------------------------------
> Fixed-regulator nowadays has preferred node-naming scheme set in the
> binding. This gets all boards on the same state for Rockchip arm32-dts.
>
> ----------------------------------------------------------------
> Johan Jonker (1):
> ARM: dts: rockchip: adapt regulator nodenames to preferred form
>
> arch/arm/boot/dts/rockchip/rk3036-kylin.dts | 2 +-
> arch/arm/boot/dts/rockchip/rk3066a-bqcurie2.dts | 4 ++--
> arch/arm/boot/dts/rockchip/rk3066a-marsboard.dts | 6 ++---
> arch/arm/boot/dts/rockchip/rk3066a-mk808.dts | 12 +++++-----
> arch/arm/boot/dts/rockchip/rk3066a-rayeager.dts | 16 ++++++-------
> arch/arm/boot/dts/rockchip/rk3128-evb.dts | 4 ++--
> arch/arm/boot/dts/rockchip/rk3128-xpi-3128.dts | 28 +++++++++++-----------
> arch/arm/boot/dts/rockchip/rk3188-bqedison2qc.dts | 14 +++++------
> arch/arm/boot/dts/rockchip/rk3188-px3-evb.dts | 2 +-
> arch/arm/boot/dts/rockchip/rk3188-radxarock.dts | 8 +++----
> arch/arm/boot/dts/rockchip/rk3228-evb.dts | 2 +-
> arch/arm/boot/dts/rockchip/rk3229-evb.dts | 16 ++++++-------
> arch/arm/boot/dts/rockchip/rk3229-xms6.dts | 16 ++++++-------
> arch/arm/boot/dts/rockchip/rk3288-evb-act8846.dts | 4 ++--
> arch/arm/boot/dts/rockchip/rk3288-evb.dtsi | 8 +++----
> .../dts/rockchip/rk3288-firefly-reload-core.dtsi | 2 +-
> .../boot/dts/rockchip/rk3288-firefly-reload.dts | 18 +++++++-------
> arch/arm/boot/dts/rockchip/rk3288-firefly.dtsi | 16 ++++++-------
> arch/arm/boot/dts/rockchip/rk3288-miqi.dts | 8 +++----
> arch/arm/boot/dts/rockchip/rk3288-phycore-rdk.dts | 6 ++---
> arch/arm/boot/dts/rockchip/rk3288-phycore-som.dtsi | 6 ++---
> arch/arm/boot/dts/rockchip/rk3288-popmetal.dts | 10 ++++----
> arch/arm/boot/dts/rockchip/rk3288-r89.dts | 8 +++----
> arch/arm/boot/dts/rockchip/rk3288-rock2-som.dtsi | 4 ++--
> arch/arm/boot/dts/rockchip/rk3288-rock2-square.dts | 6 ++---
> arch/arm/boot/dts/rockchip/rk3288-tinker.dtsi | 4 ++--
> arch/arm/boot/dts/rockchip/rk3288-veyron-brain.dts | 6 ++---
> .../dts/rockchip/rk3288-veyron-chromebook.dtsi | 10 ++++----
> arch/arm/boot/dts/rockchip/rk3288-veyron-edp.dtsi | 4 ++--
> .../arm/boot/dts/rockchip/rk3288-veyron-fievel.dts | 10 ++++----
> .../arm/boot/dts/rockchip/rk3288-veyron-mickey.dts | 4 ++--
> arch/arm/boot/dts/rockchip/rk3288-veyron-pinky.dts | 4 ++--
> arch/arm/boot/dts/rockchip/rk3288-veyron.dtsi | 8 +++----
> arch/arm/boot/dts/rockchip/rk3288-vmarc-som.dtsi | 2 +-
> arch/arm/boot/dts/rockchip/rk3288-vyasa.dts | 18 +++++++-------
> .../rockchip/rockchip-radxa-dalang-carrier.dtsi | 8 +++----
> arch/arm/boot/dts/rockchip/rv1108-elgin-r1.dts | 2 +-
> arch/arm/boot/dts/rockchip/rv1108-evb.dts | 2 +-
> .../boot/dts/rockchip/rv1126-edgeble-neu2-io.dts | 6 ++---
> .../arm/boot/dts/rockchip/rv1126-edgeble-neu2.dtsi | 2 +-
> 40 files changed, 158 insertions(+), 158 deletions(-)
>
prev parent reply other threads:[~2024-11-11 15:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 15:35 [GIT PULL] Rockchip dts32 changes for 6.13 #1 Heiko Stuebner
2024-11-11 15:36 ` Heiko Stübner [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=3580458.V25eIC5XRa@diego \
--to=heiko@sntech.de \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=soc@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;
as well as URLs for NNTP newsgroup(s).