From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
Yoshinori Sato <ysato@users.sourceforge.jp>
Cc: linux-sh@vger.kernel.org, linux-serial@vger.kernel.org,
devicetree@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH v3 00/12] ARM: shmobile: dtsi: Rename the serial port clock to fck
Date: Mon, 14 Dec 2015 19:57:54 +0100 [thread overview]
Message-ID: <1450119486-1285-1-git-send-email-geert+renesas@glider.be> (raw)
Hi Simon, Magnus, Sato-san,
This patch series renames the serial port clock to fck, cfr. "[PATCH v3
01/27] serial: sh-sci: Drop the interface clock" or series "[PATCH v3
00/27] serial: sh-sci: External Clock Support".
This series is an updated version of the DT changes of a series I sent
before as "[PATCH v2 00/16] serial: sh-sci: Clock Cleanups"
(http://www.spinics.net/lists/linux-serial/msg19762.html). To reduce
(cross) dependencies, I split off the core patches and BRG DT patches
into separate series.
Changes compared to previous submission:
- Add Acked-by,
- Update for "[PATCH 0/2] ARM: shmobile: r8a7793: Increase scif
support".
Dependencies:
- This series is against renesas-devel-20151214-v4.4-rc5, with the
following applied on top:
- "[PATCH 0/7] ARM: shmobile: dtsi: Add SCIF fallback
compatibility strings",
- It has a hard dependency on the aforementioned "[PATCH v3 01/27]
serial: sh-sci: Drop the interface clock", so depending on the
merge strategy chosen, it may have to be postponed to v4.6,
- Later series depend on this:
- "[PATCH v2 0/7] ARM: shmobile: dtsi: Add BRG support for
(H)SCIF"
- "[PATCH v2 0/9] ARM: shmobile: dts: Enable SCIF_CLK frequency
and pins".
Sato-san: I took the liberty to include the h8300 DTS changes in this
series. Perhaps you may want to provide your ack, so Simon can take it
together with the ARM shmobile changes?
Thanks!
Geert Uytterhoeven (2):
h8300: dts: Rename the serial port clock to fck
arm64: renesas: r8a7795 dtsi: Rename the serial port clock to fck
Laurent Pinchart (10):
ARM: shmobile: sh73a0 dtsi: Rename the serial port clock to fck
ARM: shmobile: r7s72100 dtsi: Rename the serial port clock to fck
ARM: shmobile: r8a73a4 dtsi: Rename the serial port clock to fck
ARM: shmobile: r8a7740 dtsi: Rename the serial port clock to fck
ARM: shmobile: r8a7778 dtsi: Rename the serial port clock to fck
ARM: shmobile: r8a7779 dtsi: Rename the serial port clock to fck
ARM: shmobile: r8a7790 dtsi: Rename the serial port clock to fck
ARM: shmobile: r8a7791 dtsi: Rename the serial port clock to fck
ARM: shmobile: r8a7793 dtsi: Rename the serial port clock to fck
ARM: shmobile: r8a7794 dtsi: Rename the serial port clock to fck
arch/arm/boot/dts/r7s72100.dtsi | 16 +++++++-------
arch/arm/boot/dts/r8a73a4.dtsi | 12 +++++------
arch/arm/boot/dts/r8a7740.dtsi | 18 ++++++++--------
arch/arm/boot/dts/r8a7778.dtsi | 12 +++++------
arch/arm/boot/dts/r8a7779.dtsi | 12 +++++------
arch/arm/boot/dts/r8a7790.dtsi | 20 +++++++++---------
arch/arm/boot/dts/r8a7791.dtsi | 36 ++++++++++++++++----------------
arch/arm/boot/dts/r8a7793.dtsi | 36 ++++++++++++++++----------------
arch/arm/boot/dts/r8a7794.dtsi | 36 ++++++++++++++++----------------
arch/arm/boot/dts/sh73a0.dtsi | 18 ++++++++--------
arch/arm64/boot/dts/renesas/r8a7795.dtsi | 22 +++++++++----------
arch/h8300/boot/dts/edosk2674.dts | 6 +++---
arch/h8300/boot/dts/h8300h_sim.dts | 4 ++--
arch/h8300/boot/dts/h8s_sim.dts | 4 ++--
14 files changed, 126 insertions(+), 126 deletions(-)
--
1.9.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:[~2015-12-14 18:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 18:57 Geert Uytterhoeven [this message]
2015-12-14 18:57 ` [PATCH v3 01/12] h8300: dts: Rename the serial port clock to fck Geert Uytterhoeven
2015-12-14 18:57 ` [PATCH v3 03/12] ARM: shmobile: r7s72100 dtsi: " Geert Uytterhoeven
2015-12-14 18:57 ` [PATCH v3 04/12] ARM: shmobile: r8a73a4 " Geert Uytterhoeven
2015-12-14 18:57 ` [PATCH v3 05/12] ARM: shmobile: r8a7740 " Geert Uytterhoeven
[not found] ` <1450119486-1285-1-git-send-email-geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org>
2015-12-14 18:57 ` [PATCH v3 02/12] ARM: shmobile: sh73a0 " Geert Uytterhoeven
2015-12-14 18:58 ` [PATCH v3 06/12] ARM: shmobile: r8a7778 " Geert Uytterhoeven
2015-12-14 18:58 ` [PATCH v3 07/12] ARM: shmobile: r8a7779 " Geert Uytterhoeven
2015-12-14 18:58 ` [PATCH v3 10/12] ARM: shmobile: r8a7793 " Geert Uytterhoeven
2015-12-14 18:58 ` [PATCH v3 08/12] ARM: shmobile: r8a7790 " Geert Uytterhoeven
2015-12-14 18:58 ` [PATCH v3 09/12] ARM: shmobile: r8a7791 " Geert Uytterhoeven
2015-12-14 18:58 ` [PATCH v3 11/12] ARM: shmobile: r8a7794 " Geert Uytterhoeven
2015-12-14 18:58 ` [PATCH v3 12/12] arm64: renesas: r8a7795 " Geert Uytterhoeven
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=1450119486-1285-1-git-send-email-geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=devicetree@vger.kernel.org \
--cc=horms@verge.net.au \
--cc=linux-serial@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=ysato@users.sourceforge.jp \
/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).