From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Ralf Baechle <ralf@linux-mips.org>,
Paul Burton <paulburton@kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Paul Cercueil <paul@crapouillou.net>,
James Hartley <james.hartley@sondrel.com>,
John Crispin <john@phrozen.org>
Cc: linux-mips@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH 0/7] MIPS: Replace <linux/clk-provider.h> by <linux/of_clk.h>
Date: Wed, 12 Feb 2020 11:15:37 +0100 [thread overview]
Message-ID: <20200212101544.8793-1-geert+renesas@glider.be> (raw)
Hi all,
The OF clock helpers were moved to <linux/of_clk.h> a while ago.
Hence code that is not a clock provider, but just needs to call
of_clk_init(), can (and should) include <linux/of_clk.h> instead of
<linux/clk-provider.h>.
All these patches are independent of each others, and thus can be
applied by the corresponding subsystem maintainers.
Thanks!
Geert Uytterhoeven (7):
MIPS: ath79: Replace <linux/clk-provider.h> by <linux/of_clk.h>
MIPS: BMIPS: Replace <linux/clk-provider.h> by <linux/of_clk.h>
MIPS: generic: Replace <linux/clk-provider.h> by <linux/of_clk.h>
MIPS: jz4740: Replace <linux/clk-provider.h> by <linux/of_clk.h>
MIPS: pic32mzda: Replace <linux/clk-provider.h> by <linux/of_clk.h>
MIPS: Pistachio: Replace <linux/clk-provider.h> by <linux/of_clk.h>
MIPS: ralink: Replace <linux/clk-provider.h> by <linux/of_clk.h>
arch/mips/ath79/setup.c | 2 +-
arch/mips/bmips/setup.c | 2 +-
arch/mips/generic/init.c | 2 +-
arch/mips/jz4740/time.c | 2 +-
arch/mips/pic32/pic32mzda/time.c | 2 +-
arch/mips/pistachio/time.c | 2 +-
arch/mips/ralink/timer-gic.c | 2 +-
7 files changed, 7 insertions(+), 7 deletions(-)
--
2.17.1
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next reply other threads:[~2020-02-12 10:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 10:15 Geert Uytterhoeven [this message]
2020-02-12 10:15 ` [PATCH 1/7] MIPS: ath79: Replace <linux/clk-provider.h> by <linux/of_clk.h> Geert Uytterhoeven
2020-02-12 18:52 ` Stephen Boyd
2020-02-12 10:15 ` [PATCH 2/7] MIPS: BMIPS: " Geert Uytterhoeven
2020-02-12 17:45 ` Florian Fainelli
2020-02-12 18:53 ` Stephen Boyd
2020-02-12 10:15 ` [PATCH 3/7] MIPS: generic: " Geert Uytterhoeven
2020-02-12 20:52 ` Stephen Boyd
2020-02-12 10:15 ` [PATCH 4/7] MIPS: jz4740: " Geert Uytterhoeven
2020-02-12 20:52 ` Stephen Boyd
2020-02-13 15:36 ` Paul Cercueil
2020-02-12 10:15 ` [PATCH 5/7] MIPS: pic32mzda: " Geert Uytterhoeven
2020-02-12 20:52 ` Stephen Boyd
2020-02-12 10:15 ` [PATCH 6/7] MIPS: Pistachio: " Geert Uytterhoeven
2020-02-12 20:53 ` Stephen Boyd
2020-02-12 22:08 ` James Hartley
2020-02-12 10:15 ` [PATCH 7/7] MIPS: ralink: " Geert Uytterhoeven
2020-02-12 20:53 ` Stephen Boyd
2020-02-13 4:35 ` John Crispin
2020-02-12 18:41 ` [PATCH 0/7] MIPS: " Philippe Mathieu-Daudé
2020-02-19 19:04 ` Paul Burton
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=20200212101544.8793-1-geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=james.hartley@sondrel.com \
--cc=john@phrozen.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=paul@crapouillou.net \
--cc=paulburton@kernel.org \
--cc=ralf@linux-mips.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).