From: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
To: Andy Yan <andy.yan-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
ulf.hansson-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
linux-mmc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH 1/7] dt-bindings: rockchip-dw-mshc: rename RK1108 to RV1108
Date: Thu, 23 Feb 2017 15:59:49 +0100 [thread overview]
Message-ID: <4846582.IXrHj1lV7W@phil> (raw)
In-Reply-To: <1486983759-32337-1-git-send-email-andy.yan-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
Am Montag, 13. Februar 2017, 19:02:39 CET schrieb Andy Yan:
> Rockchip finally named the SOC as RV1108, so change it.
>
> Signed-off-by: Andy Yan <andy.yan-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
Reviewed-by: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
next prev parent reply other threads:[~2017-02-23 14:59 UTC|newest]
Thread overview: 22+ 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:02 ` [PATCH 1/7] dt-bindings: rockchip-dw-mshc: rename " Andy Yan
[not found] ` <1486983759-32337-1-git-send-email-andy.yan-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-02-14 8:51 ` Ulf Hansson
2017-02-21 23:36 ` Rob Herring
2017-02-22 1:51 ` Heiko Stuebner
2017-02-23 14:59 ` Heiko Stuebner [this message]
2017-03-14 16:20 ` Ulf Hansson
2017-02-13 11:04 ` [PATCH 2/7] dt-bindings: rk1108-cru: " Andy Yan
[not found] ` <1486983857-32399-1-git-send-email-andy.yan-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-02-22 20:47 ` Rob Herring
[not found] ` <1486983566-32265-1-git-send-email-andy.yan-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
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
[not found] ` <1486983983-32506-1-git-send-email-andy.yan-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
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:09 ` [PATCH 6/7] ARM: dts: " Andy Yan
2017-02-13 11:10 ` [PATCH 7/7] ARM: rockchip: reanme " Andy Yan
[not found] ` <1486984234-32693-1-git-send-email-andy.yan-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-02-22 15:10 ` Rob Herring
2017-02-13 12:51 ` [PATCH 0/7] Rename " Heiko Stuebner
2017-02-14 0:44 ` 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=4846582.IXrHj1lV7W@phil \
--to=heiko-4mtyjxux2i+zqb+pc5nmwq@public.gmane.org \
--cc=andy.yan-TNX95d0MmH7DzftRWevZcw@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-mmc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=ulf.hansson-QSEj5FYQhm4dnm+yROfE0A@public.gmane.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).