All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Stuebner <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.1 #2
Date: Wed, 23 Nov 2022 15:00:07 +0100	[thread overview]
Message-ID: <3721014.iZASKD2KPV@phil> (raw)
In-Reply-To: <9661382.T7Z3S40VBb@phil>

Am Mittwoch, 23. November 2022, 14:50:34 CET schrieb Heiko Stuebner:

The subject was supposed to be "#1" not "#2".
Sorry about that

Heiko

> The following changes since commit 9abf2313adc1ca1b6180c508c25f22f9395cc780:
> 
>   Linux 6.1-rc1 (2022-10-16 15:36:24 -0700)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v6.2-rockchip-dts32-1
> 
> for you to fetch changes up to da74858a475782a3f16470907814c8cc5950ad68:
> 
>   ARM: dts: rockchip: disable arm_global_timer on rk3066 and rk3188 (2022-11-15 12:02:38 +0100)
> 
> ----------------------------------------------------------------
> Disabling of the unreliable arm-global-timer on earliest
> Rockchip SoCs, due to its frequency being bound to the
> changing cpu clock.
> 
> ----------------------------------------------------------------
> Johan Jonker (1):
>       ARM: dts: rockchip: disable arm_global_timer on rk3066 and rk3188
> 
>  arch/arm/boot/dts/rk3188.dtsi | 1 -
>  arch/arm/boot/dts/rk3xxx.dtsi | 7 +++++++
>  2 files changed, 7 insertions(+), 1 deletion(-)
> 





_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <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.1 #2
Date: Wed, 23 Nov 2022 15:00:07 +0100	[thread overview]
Message-ID: <3721014.iZASKD2KPV@phil> (raw)
In-Reply-To: <9661382.T7Z3S40VBb@phil>

Am Mittwoch, 23. November 2022, 14:50:34 CET schrieb Heiko Stuebner:

The subject was supposed to be "#1" not "#2".
Sorry about that

Heiko

> The following changes since commit 9abf2313adc1ca1b6180c508c25f22f9395cc780:
> 
>   Linux 6.1-rc1 (2022-10-16 15:36:24 -0700)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v6.2-rockchip-dts32-1
> 
> for you to fetch changes up to da74858a475782a3f16470907814c8cc5950ad68:
> 
>   ARM: dts: rockchip: disable arm_global_timer on rk3066 and rk3188 (2022-11-15 12:02:38 +0100)
> 
> ----------------------------------------------------------------
> Disabling of the unreliable arm-global-timer on earliest
> Rockchip SoCs, due to its frequency being bound to the
> changing cpu clock.
> 
> ----------------------------------------------------------------
> Johan Jonker (1):
>       ARM: dts: rockchip: disable arm_global_timer on rk3066 and rk3188
> 
>  arch/arm/boot/dts/rk3188.dtsi | 1 -
>  arch/arm/boot/dts/rk3xxx.dtsi | 7 +++++++
>  2 files changed, 7 insertions(+), 1 deletion(-)
> 





WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <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.1 #2
Date: Wed, 23 Nov 2022 15:00:07 +0100	[thread overview]
Message-ID: <3721014.iZASKD2KPV@phil> (raw)
In-Reply-To: <9661382.T7Z3S40VBb@phil>

Am Mittwoch, 23. November 2022, 14:50:34 CET schrieb Heiko Stuebner:

The subject was supposed to be "#1" not "#2".
Sorry about that

Heiko

> The following changes since commit 9abf2313adc1ca1b6180c508c25f22f9395cc780:
> 
>   Linux 6.1-rc1 (2022-10-16 15:36:24 -0700)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v6.2-rockchip-dts32-1
> 
> for you to fetch changes up to da74858a475782a3f16470907814c8cc5950ad68:
> 
>   ARM: dts: rockchip: disable arm_global_timer on rk3066 and rk3188 (2022-11-15 12:02:38 +0100)
> 
> ----------------------------------------------------------------
> Disabling of the unreliable arm-global-timer on earliest
> Rockchip SoCs, due to its frequency being bound to the
> changing cpu clock.
> 
> ----------------------------------------------------------------
> Johan Jonker (1):
>       ARM: dts: rockchip: disable arm_global_timer on rk3066 and rk3188
> 
>  arch/arm/boot/dts/rk3188.dtsi | 1 -
>  arch/arm/boot/dts/rk3xxx.dtsi | 7 +++++++
>  2 files changed, 7 insertions(+), 1 deletion(-)
> 





_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-11-23 14:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-23 13:50 [GIT PULL] Rockchip dts32 changes for 6.1 #2 Heiko Stuebner
2022-11-23 13:50 ` Heiko Stuebner
2022-11-23 13:50 ` Heiko Stuebner
2022-11-23 14:00 ` Heiko Stuebner [this message]
2022-11-23 14:00   ` Heiko Stuebner
2022-11-23 14:00   ` Heiko Stuebner
2022-11-24 15:20 ` patchwork-bot+linux-soc

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=3721014.iZASKD2KPV@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.