From: Icenowy Zheng <icenowy@aosc.xyz>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
"linux-sunxi@googlegroups.com" <linux-sunxi@googlegroups.com>,
Stephen Boyd <sboyd@codeaurora.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Chen-Yu Tsai <wens@csie.org>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 2/5] clk: sunxi-ng: add support for V3s CCU
Date: Thu, 12 Jan 2017 03:39:53 +0800 [thread overview]
Message-ID: <2705031484163593@web1g.yandex.ru> (raw)
In-Reply-To: <20170110181006.yrd6moy2mctzoc4c@lukather>
CgoxMS4wMS4yMDE3LCAwMjoxMCwgIk1heGltZSBSaXBhcmQiIDxtYXhpbWUucmlwYXJkQGZyZWUt
ZWxlY3Ryb25zLmNvbT46Cj4gT24gVHVlLCBKYW4gMDMsIDIwMTcgYXQgMTE6MTY6MjZQTSArMDgw
MCwgSWNlbm93eSBaaGVuZyB3cm90ZToKPj4gwqBWM3MgaGFzIGEgc2ltaWxhciBidXQgY3V0LWRv
d24gQ0NVIHRvIEgzLgo+Pgo+PiDCoEFkZCBzdXBwb3J0IGZvciBpdC4KPj4KPj4gwqBTaWduZWQt
b2ZmLWJ5OiBJY2Vub3d5IFpoZW5nIDxpY2Vub3d5QGFvc2MueHl6Pgo+Cj4gSXQgbG9va3MgbGlr
ZSB0aGVyZSdzIG5vdGhpbmcgZGlmZmVyZW50IGJ1dCB0aGUgY2xvY2tzIHRoYXQgeW91Cj4gcmVn
aXN0ZXIgd2l0aCB0aGUgSDMsIHBsZWFzZSBqdXN0IHVzZSB0aGUgSDMgZHJpdmVyLgoKTm9wZS4K
Ckl0IGhhcyBhIGRpZmZlcmVudCBQTEwgKFBMTF9JU1ApIGF0IGRpZmZlcmVudCBhZGRyZXNzLCBh
bmQgc29tZQpkaWZmZXJlbnQgbXV4ZXMuCgo+Cj4gVGhhbmtzIQo+IE1heGltZQo+Cj4gLS0KPiBN
YXhpbWUgUmlwYXJkLCBGcmVlIEVsZWN0cm9ucwo+IEVtYmVkZGVkIExpbnV4IGFuZCBLZXJuZWwg
ZW5naW5lZXJpbmcKPiBodHRwOi8vZnJlZS1lbGVjdHJvbnMuY29tCgpfX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpsaW51eC1hcm0ta2VybmVsIG1haWxpbmcg
bGlzdApsaW51eC1hcm0ta2VybmVsQGxpc3RzLmluZnJhZGVhZC5vcmcKaHR0cDovL2xpc3RzLmlu
ZnJhZGVhZC5vcmcvbWFpbG1hbi9saXN0aW5mby9saW51eC1hcm0ta2VybmVsCg==
next prev parent reply other threads:[~2017-01-11 19:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-03 15:16 [PATCH 0/5] add support for Allwinner V3s SoC Icenowy Zheng
2017-01-03 15:16 ` [PATCH 1/5] arm: sunxi: add support for " Icenowy Zheng
2017-01-10 18:09 ` Maxime Ripard
2017-01-11 19:40 ` Icenowy Zheng
2017-01-12 17:17 ` Maxime Ripard
2017-01-03 15:16 ` [PATCH 2/5] clk: sunxi-ng: add support for V3s CCU Icenowy Zheng
2017-01-10 18:10 ` Maxime Ripard
2017-01-11 19:39 ` Icenowy Zheng [this message]
2017-01-11 19:44 ` Icenowy Zheng
2017-01-12 17:19 ` Maxime Ripard
2017-01-03 15:16 ` [PATCH 3/5] pinctrl: sunxi: add driver for V3s SoC Icenowy Zheng
2017-01-10 18:18 ` Maxime Ripard
2017-01-11 15:24 ` Linus Walleij
2017-01-03 15:16 ` [PATCH 4/5] ARM: dts: sunxi: add dtsi file " Icenowy Zheng
2017-01-10 18:21 ` Maxime Ripard
2017-01-03 15:16 ` [PATCH 5/5] ARM: dts: sunxi: add support for Lichee Pi Zero board Icenowy Zheng
[not found] <20170112203149.VhtuR9dM@smtp3j.mail.yandex.net>
2017-01-12 17:41 ` [PATCH 2/5] clk: sunxi-ng: add support for V3s CCU Maxime Ripard
2017-01-13 4:36 ` Icenowy 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=2705031484163593@web1g.yandex.ru \
--to=icenowy@aosc.xyz \
--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-doc@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=maxime.ripard@free-electrons.com \
--cc=sboyd@codeaurora.org \
--cc=wens@csie.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