From: Heiko Stuebner <heiko@sntech.de>
To: Andy Yan <andy.yan@rock-chips.com>, robh+dt@kernel.org
Cc: linus.walleij@linaro.org, shawn.lin@rock-chips.com,
linux-clk@vger.kernel.org, linux-rockchip@lists.infradead.org,
devicetree@vger.kernel.org, sboyd@codeaurora.org,
linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/7] Rename RK1108 to RV1108
Date: Mon, 13 Feb 2017 13:51:53 +0100 [thread overview]
Message-ID: <2809087.MHZWQWdaOC@phil> (raw)
In-Reply-To: <1486983566-32265-1-git-send-email-andy.yan@rock-chips.com>
Hi Andy,
Am Montag, 13. Februar 2017, 18:59:26 CET schrieb Andy Yan:
> Rockchip finally named this soc as RV1108, so change
> RK1108/rk1108 to RV1108/rv1108 for compatible.
renaming existing bindings (that have been in multiple kernel versions
already) always is a hot topic. So I'll be hoping for Rob to give a go-ahead
for it :-) .
Just to confirm, the rk1108/rv1108 is completely new to the market, so we're
not breaking any existing devices, right?
Heiko
> Andy Yan (7):
> dt-bindings: rockchip-dw-mshc: rename RK1108 to RV1108
> dt-bindings: rk1108-cru: rename RK1108 to RV1108
> clk: rockchip: rename RK1108 to RV1108
> dt-bindings: rockchip,pinctrl: rename RK1108 to RV1108
> pinctrl: rockchip: rename RK1108 to RV1108
> ARM: dts: rename RK1108 to RV1108
> ARM: rockchip: reanme RK1108 to RV1108
>
> Documentation/devicetree/bindings/arm/rockchip.txt | 4 +-
> ...chip,rk1108-cru.txt => rockchip,rv1108-cru.txt} | 12 +-
> .../devicetree/bindings/mmc/rockchip-dw-mshc.txt | 2 +-
> .../bindings/pinctrl/rockchip,pinctrl.txt | 16 +-
> arch/arm/boot/dts/Makefile | 2 +-
> .../boot/dts/{rk1108-evb.dts => rv1108-evb.dts} | 7 +-
> arch/arm/boot/dts/{rk1108.dtsi => rv1108.dtsi} | 24 +-
> drivers/clk/rockchip/Makefile | 2 +-
> .../clk/rockchip/{clk-rk1108.c => clk-rv1108.c} | 414
> ++++++++++----------- drivers/clk/rockchip/clk.h |
> 28 +-
> drivers/pinctrl/pinctrl-rockchip.c | 76 ++--
> .../clock/{rk1108-cru.h => rv1108-cru.h} | 6 +-
> 12 files changed, 300 insertions(+), 293 deletions(-)
> rename Documentation/devicetree/bindings/clock/{rockchip,rk1108-cru.txt =>
> rockchip,rv1108-cru.txt} (83%) rename arch/arm/boot/dts/{rk1108-evb.dts =>
> rv1108-evb.dts} (89%) rename arch/arm/boot/dts/{rk1108.dtsi => rv1108.dtsi}
> (94%)
> rename drivers/clk/rockchip/{clk-rk1108.c => clk-rv1108.c} (57%)
> rename include/dt-bindings/clock/{rk1108-cru.h => rv1108-cru.h} (97%)
next prev parent reply other threads:[~2017-02-13 12:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 10:59 [PATCH 0/7] Rename RK1108 to RV1108 Andy Yan
2017-02-13 11:07 ` [PATCH 5/7] pinctrl: rockchip: rename " Andy Yan
2017-02-22 18:34 ` Heiko Stuebner
2017-02-13 12:51 ` Heiko Stuebner [this message]
2017-02-14 0:44 ` [PATCH 0/7] Rename " Andy Yan
2017-02-23 10:15 ` Linus Walleij
[not found] ` <CACRpkdbNbGvwUq3uLgekimOwzBZCXf37JW9LCCqLm1so=CMNrw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-02-23 15:00 ` Heiko Stuebner
2017-03-14 13:36 ` Linus Walleij
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=2809087.MHZWQWdaOC@phil \
--to=heiko@sntech.de \
--cc=andy.yan@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=shawn.lin@rock-chips.com \
/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).