From: Ulf Hansson <ulf.hansson@linaro.org>
To: Andy Yan <andy.yan@rock-chips.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/7] dt-bindings: rockchip-dw-mshc: rename RK1108 to RV1108
Date: Tue, 14 Feb 2017 09:51:26 +0100 [thread overview]
Message-ID: <CAPDyKFqcNNEnfgyLg9-+PamstuFJOQ5kEmEcZ3x97XC2qXC54g@mail.gmail.com> (raw)
In-Reply-To: <1486983759-32337-1-git-send-email-andy.yan@rock-chips.com>
On 13 February 2017 at 12:02, Andy Yan <andy.yan@rock-chips.com> wrote:
> Rockchip finally named the SOC as RV1108, so change it.
>
> Signed-off-by: Andy Yan <andy.yan@rock-chips.com>
>
> ---
>
> Documentation/devicetree/bindings/mmc/rockchip-dw-mshc.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/mmc/rockchip-dw-mshc.txt b/Documentation/devicetree/bindings/mmc/rockchip-dw-mshc.txt
> index ea9c1c9..520d61d 100644
> --- a/Documentation/devicetree/bindings/mmc/rockchip-dw-mshc.txt
> +++ b/Documentation/devicetree/bindings/mmc/rockchip-dw-mshc.txt
> @@ -13,7 +13,7 @@ Required Properties:
> - "rockchip,rk2928-dw-mshc": for Rockchip RK2928 and following,
> before RK3288
> - "rockchip,rk3288-dw-mshc": for Rockchip RK3288
> - - "rockchip,rk1108-dw-mshc", "rockchip,rk3288-dw-mshc": for Rockchip RK1108
> + - "rockchip,rv1108-dw-mshc", "rockchip,rk3288-dw-mshc": for Rockchip RV1108
> - "rockchip,rk3036-dw-mshc", "rockchip,rk3288-dw-mshc": for Rockchip RK3036
> - "rockchip,rk3368-dw-mshc", "rockchip,rk3288-dw-mshc": for Rockchip RK3368
> - "rockchip,rk3399-dw-mshc", "rockchip,rk3288-dw-mshc": for Rockchip RK3399
> --
> 2.7.4
>
>
Seems like we didn't really start to use the previous compatible
string, so I am fine with changing this. Anyway, I need an ack from
Rob.
Kind regards
Uffe
next prev parent reply other threads:[~2017-02-14 8:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1486983566-32265-1-git-send-email-andy.yan@rock-chips.com>
2017-02-13 11:02 ` [PATCH 1/7] dt-bindings: rockchip-dw-mshc: rename RK1108 to RV1108 Andy Yan
2017-02-14 8:51 ` Ulf Hansson [this message]
2017-02-21 23:36 ` Rob Herring
2017-02-22 1:51 ` Heiko Stuebner
2017-02-23 14:59 ` Heiko Stuebner
2017-03-14 16:20 ` Ulf Hansson
2017-02-13 11:04 ` [PATCH 2/7] dt-bindings: rk1108-cru: " Andy Yan
2017-02-22 20:47 ` Rob Herring
2017-02-13 11:04 ` [PATCH 3/7] clk: rockchip: " Andy Yan
2017-02-13 11:06 ` [PATCH 4/7] dt-bindings: rockchip,pinctrl: " Andy Yan
2017-02-22 15:08 ` Rob Herring
2017-02-22 18:33 ` Heiko Stuebner
2017-03-14 13:26 ` Linus Walleij
2017-02-13 11:07 ` [PATCH 5/7] pinctrl: rockchip: " Andy Yan
2017-02-22 18:34 ` Heiko Stuebner
2017-02-13 11:09 ` [PATCH 6/7] ARM: dts: " Andy Yan
2017-02-13 11:10 ` [PATCH 7/7] ARM: rockchip: reanme " Andy Yan
2017-02-22 15:10 ` Rob Herring
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=CAPDyKFqcNNEnfgyLg9-+PamstuFJOQ5kEmEcZ3x97XC2qXC54g@mail.gmail.com \
--to=ulf.hansson@linaro.org \
--cc=andy.yan@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@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: 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).