From: Heiko Stuebner <heiko@sntech.de>
To: Xing Zheng <zhengxing@rock-chips.com>
Cc: linux-rockchip@lists.infradead.org,
Russell King <linux@arm.linux.org.uk>,
Michael Turquette <mturquette@baylibre.com>,
devicetree@vger.kernel.org, Stephen Boyd <sboyd@codeaurora.org>,
linux-gpio@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Kumar Gala <galak@codeaurora.org>,
linux-kernel@vger.kernel.org,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v1 0/3] Port and support rk3036 SoC platform
Date: Fri, 28 Aug 2015 11:59:59 +0200 [thread overview]
Message-ID: <6551991.RUDkGfdSCp@phil> (raw)
In-Reply-To: <1440740808-15004-1-git-send-email-zhengxing@rock-chips.com>
Hi,
Am Freitag, 28. August 2015, 13:46:45 schrieb Xing Zheng:
> We need to support rk3036 soc platform via upstream, there are
> 3 parts for the initial release of minimum system: dts, pinctrl,
> and clock tree for rk3036, startup and run to init processs.
this is really cool that you're working on supporting the rk3036.
I had some comments to the individual patches, but overall it looks quite nice
already.
So, thanks for working on this
Heiko
next prev parent reply other threads:[~2015-08-28 9:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 5:46 [PATCH v1 0/3] Port and support rk3036 SoC platform Xing Zheng
2015-08-28 5:46 ` [PATCH v1 2/3] pinctrl: rockchip: add support for the rk3036 Xing Zheng
2015-08-28 7:53 ` Heiko Stuebner
2015-09-25 16:25 ` Linus Walleij
2015-08-28 9:59 ` Heiko Stuebner [this message]
2015-08-28 10:07 ` [PATCH v1 0/3] Port and support rk3036 SoC platform Xing Zheng
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=6551991.RUDkGfdSCp@phil \
--to=heiko@sntech.de \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--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-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=zhengxing@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).