From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Russell King <linux@armlinux.org.uk>,
Matthias Brugger <matthias.bgg@gmail.com>,
Lubomir Rintel <lkundrak@v3.sk>, Heiko Stuebner <heiko@sntech.de>,
Magnus Damm <magnus.damm@gmail.com>,
Maxime Ripard <mripard@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
Michal Simek <michal.simek@xilinx.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
linux-rockchip@lists.infradead.org,
linux-renesas-soc@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH 7/7] ARM: zynq: Replace <linux/clk-provider.h> by <linux/of_clk.h>
Date: Wed, 12 Feb 2020 11:08:30 +0100 [thread overview]
Message-ID: <20200212100830.446-8-geert+renesas@glider.be> (raw)
In-Reply-To: <20200212100830.446-1-geert+renesas@glider.be>
The Zynq platform code is not a clock provider, and just needs to call
of_clk_init().
Hence it can include <linux/of_clk.h> instead of <linux/clk-provider.h>.
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
---
arch/arm/mach-zynq/common.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-zynq/common.c b/arch/arm/mach-zynq/common.c
index 3a4248fd796281c3..a9dd2f71cd19d2a9 100644
--- a/arch/arm/mach-zynq/common.c
+++ b/arch/arm/mach-zynq/common.c
@@ -12,10 +12,10 @@
#include <linux/cpumask.h>
#include <linux/platform_device.h>
#include <linux/clk.h>
-#include <linux/clk-provider.h>
#include <linux/clk/zynq.h>
#include <linux/clocksource.h>
#include <linux/of_address.h>
+#include <linux/of_clk.h>
#include <linux/of_irq.h>
#include <linux/of_platform.h>
#include <linux/of.h>
--
2.17.1
next prev parent reply other threads:[~2020-02-12 10:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 10:08 [PATCH 0/7] ARM: Replace <linux/clk-provider.h> by <linux/of_clk.h> Geert Uytterhoeven
2020-02-12 10:08 ` [PATCH 1/7] ARM/time: " Geert Uytterhoeven
2020-02-12 17:08 ` Stephen Boyd
2020-02-12 10:08 ` [PATCH 2/7] ARM: mediatek: " Geert Uytterhoeven
2020-02-12 17:08 ` Stephen Boyd
2020-02-12 10:08 ` [PATCH 3/7] ARM: mmp: " Geert Uytterhoeven
2020-02-12 17:09 ` Stephen Boyd
2020-02-12 10:08 ` [PATCH 4/7] ARM: rockchip: " Geert Uytterhoeven
2020-02-12 13:38 ` Heiko Stuebner
2020-02-12 17:09 ` Stephen Boyd
2020-02-12 10:08 ` [PATCH 5/7] ARM: shmobile: " Geert Uytterhoeven
2020-02-12 17:09 ` Stephen Boyd
2020-02-12 10:08 ` [PATCH 6/7] ARM: sunxi: " Geert Uytterhoeven
2020-02-12 17:09 ` Stephen Boyd
2020-02-12 17:15 ` Maxime Ripard
2020-02-12 10:08 ` Geert Uytterhoeven [this message]
2020-02-12 11:14 ` [PATCH 7/7] ARM: zynq: " Michal Simek
2020-02-12 17:10 ` 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=20200212100830.446-8-geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=lkundrak@v3.sk \
--cc=magnus.damm@gmail.com \
--cc=matthias.bgg@gmail.com \
--cc=michal.simek@xilinx.com \
--cc=mripard@kernel.org \
--cc=wens@csie.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).