From: Heiko Stuebner <heiko@sntech.de> To: arm@kernel.org Cc: linux-rockchip@lists.infradead.org, soc@kernel.org, linux-arm-kernel@lists.infradead.org Subject: [GIT PULL 3/3] Rockchip soc32 changes for 5.8 Date: Thu, 21 May 2020 03:18:55 +0200 [thread overview] Message-ID: <2307012.mB7vfBFN1M@phil> (raw) In-Reply-To: <1970481.V9vR1fIhX2@phil> The following changes since commit 8f3d9f354286745c751374f5f1fcafee6b3f3136: Linux 5.7-rc1 (2020-04-12 12:35:55 -0700) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v5.8-rockchip-soc32-1 for you to fetch changes up to 0b973c65d2f2da049252bc8370e4cf037b99c7e9: ARM: rockchip: fix spelling mistake "to" -> "too" (2020-04-13 09:40:45 +0200) ---------------------------------------------------------------- A spelling fix and stop using clk_provider.h when of_clk.h is enough as the soc file is only a clock user, not a provider. ---------------------------------------------------------------- Colin Ian King (1): ARM: rockchip: fix spelling mistake "to" -> "too" Geert Uytterhoeven (1): ARM: rockchip: Replace <linux/clk-provider.h> by <linux/of_clk.h> arch/arm/mach-rockchip/platsmp.c | 2 +- arch/arm/mach-rockchip/rockchip.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de> To: arm@kernel.org Cc: linux-rockchip@lists.infradead.org, soc@kernel.org, linux-arm-kernel@lists.infradead.org Subject: [GIT PULL 3/3] Rockchip soc32 changes for 5.8 Date: Thu, 21 May 2020 03:18:55 +0200 [thread overview] Message-ID: <2307012.mB7vfBFN1M@phil> (raw) In-Reply-To: <1970481.V9vR1fIhX2@phil> The following changes since commit 8f3d9f354286745c751374f5f1fcafee6b3f3136: Linux 5.7-rc1 (2020-04-12 12:35:55 -0700) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v5.8-rockchip-soc32-1 for you to fetch changes up to 0b973c65d2f2da049252bc8370e4cf037b99c7e9: ARM: rockchip: fix spelling mistake "to" -> "too" (2020-04-13 09:40:45 +0200) ---------------------------------------------------------------- A spelling fix and stop using clk_provider.h when of_clk.h is enough as the soc file is only a clock user, not a provider. ---------------------------------------------------------------- Colin Ian King (1): ARM: rockchip: fix spelling mistake "to" -> "too" Geert Uytterhoeven (1): ARM: rockchip: Replace <linux/clk-provider.h> by <linux/of_clk.h> arch/arm/mach-rockchip/platsmp.c | 2 +- arch/arm/mach-rockchip/rockchip.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) _______________________________________________ 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:[~2020-05-21 1:18 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-21 1:17 [GIT PULL 1/3] Rockchip dt64 changes for 5.8 Heiko Stuebner 2020-05-21 1:17 ` Heiko Stuebner 2020-05-21 1:17 ` [GIT PULL 2/3] Rockchip dt32 " Heiko Stuebner 2020-05-21 1:17 ` Heiko Stuebner 2020-05-21 1:18 ` Heiko Stuebner [this message] 2020-05-21 1:18 ` [GIT PULL 3/3] Rockchip soc32 " 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=2307012.mB7vfBFN1M@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: linkBe 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.