From: 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 5.18 #1
Date: Thu, 10 Mar 2022 02:39:51 +0100 [thread overview]
Message-ID: <37432054.P6GNo21ksS@phil> (raw)
In-Reply-To: <3788968.RB9BLzCXGK@phil>
Correction: The mail subject was supposed to be "#2"
Heiko
Am Donnerstag, 10. März 2022, 02:38:50 CET schrieb Heiko Stuebner:
> The following changes since commit 5a68ce0a7b89a7005a71d406435a45a24c7e86da:
>
> ARM: dts: rockchip: remove status from rk3288 crypto node (2022-02-15 08:59:53 +0100)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v5.18-rockchip-dts32-2
>
> for you to fetch changes up to c042639a70ed00ab2138f507ae1d6fa57c66ce11:
>
> ARM: dts: rockchip: Update regulator name for PX3 (2022-03-05 18:17:08 +0100)
>
> ----------------------------------------------------------------
> Some fixes for rk8xx pmics to make them follow
> the dt-binding better.
>
> ----------------------------------------------------------------
> Chris Morgan (2):
> ARM: dts: rockchip: Add #clock-cells value for rk805
> ARM: dts: rockchip: Update regulator name for PX3
>
> arch/arm/boot/dts/rk3188-px3-evb.dts | 2 +-
> arch/arm/boot/dts/rv1108-elgin-r1.dts | 1 +
> arch/arm/boot/dts/rv1108-evb.dts | 1 +
> 3 files changed, 3 insertions(+), 1 deletion(-)
>
_______________________________________________
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-03-10 1:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 1:38 [GIT PULL] Rockchip dts32 changes for 5.18 #1 Heiko Stuebner
2022-03-10 1:39 ` heiko [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-24 23:19 Heiko Stuebner
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=37432054.P6GNo21ksS@phil \
--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).