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 1/5] arm: sunxi: add support for V3s SoC
Date: Thu, 12 Jan 2017 03:40:32 +0800 [thread overview]
Message-ID: <2706391484163632@web1g.yandex.ru> (raw)
In-Reply-To: <20170110180926.ilqtygttpfgbetvu@lukather>
CgoxMS4wMS4yMDE3LCAwMjowOSwgIk1heGltZSBSaXBhcmQiIDxtYXhpbWUucmlwYXJkQGZyZWUt
ZWxlY3Ryb25zLmNvbT46Cj4gT24gVHVlLCBKYW4gMDMsIDIwMTcgYXQgMTE6MTY6MjVQTSArMDgw
MCwgSWNlbm93eSBaaGVuZyB3cm90ZToKPj4gwqBBbGx3aW5uZXIgVjNzIGlzIGEgbG93LWVuZCBz
aW5nbGUtY29yZSBDb3J0ZXgtQTcgU29DLCB3aXRoIDY0TUIKPj4gwqBpbnRlZ3JhdGVkIERSQU0s
IGFuZCBzZXZlcmFsIHBlcmlwaGVyYWxzLgo+Pgo+PiDCoFNpZ25lZC1vZmYtYnk6IEljZW5vd3kg
WmhlbmcgPGljZW5vd3lAYW9zYy54eXo+Cj4+IMKgLS0tCj4+IMKgwqBEb2N1bWVudGF0aW9uL2Fy
bS9zdW54aS9SRUFETUUgfCA0ICsrKysKPj4gwqDCoGFyY2gvYXJtL21hY2gtc3VueGkvc3VueGku
YyB8IDEgKwo+PiDCoMKgMiBmaWxlcyBjaGFuZ2VkLCA1IGluc2VydGlvbnMoKykKPj4KPj4gwqBk
aWZmIC0tZ2l0IGEvRG9jdW1lbnRhdGlvbi9hcm0vc3VueGkvUkVBRE1FIGIvRG9jdW1lbnRhdGlv
bi9hcm0vc3VueGkvUkVBRE1FCj4+IMKgaW5kZXggY2QwMjQzMzAyYmMxLi45MWVjOGYyMDU1YmUg
MTAwNjQ0Cj4+IMKgLS0tIGEvRG9jdW1lbnRhdGlvbi9hcm0vc3VueGkvUkVBRE1FCj4+IMKgKysr
IGIvRG9jdW1lbnRhdGlvbi9hcm0vc3VueGkvUkVBRE1FCj4+IMKgQEAgLTY3LDYgKzY3LDEwIEBA
IFN1blhpIGZhbWlseQo+PiDCoMKgwqDCoMKgwqDCoMKgwqDCoCsgRGF0YXNoZWV0Cj4+IMKgwqDC
oMKgwqDCoMKgwqDCoMKgwqDCoGh0dHA6Ly9kbC5saW51eC1zdW54aS5vcmcvSDMvQWxsd2lubmVy
X0gzX0RhdGFzaGVldF9WMS4wLnBkZgo+Pgo+PiDCoCsgLSBBbGx3aW5uZXIgVjNzIChzdW44aSkK
Pj4gwqArICsgRGF0YXNoZWV0Cj4+IMKgKyBodHRwczovL3d3dy5nb3ByYXduLmNvbS9mb3J1bS9h
bGx3aW5uZXItY2Ftcy83ODMtYWxsd2lubmVyLXYzcy1zb2MtZGF0YXNoZWV0Cj4+IMKgKwo+Cj4g
UGxlYXNlIGRvbid0IHB1dCByYW5kb20gbGlua3MgaW4gdGhlcmUsIGJ1dCBhdCBsZWFzdCBzb21l
dGhpbmcgdGhhdCB3ZQo+IGtub3cgd2lsbCBiZSB0aGVyZSBpbiBhIGNvdXBsZSBvZiB3ZWVrcy9t
b250aGVzL3llYXJzCgpJcyBodHRwOi8vbGludXgtc3VueGkub3JnL0ZpbGU6QWxsd2lubmVyX1Yz
c19EYXRhc2hlZXRfVjEuMC5wZGYgYWNjZXB0YWJsZT8KCj4KPiBUaGFua3MsCj4gTWF4aW1lCj4K
PiAtLQo+IE1heGltZSBSaXBhcmQsIEZyZWUgRWxlY3Ryb25zCj4gRW1iZWRkZWQgTGludXggYW5k
IEtlcm5lbCBlbmdpbmVlcmluZwo+IGh0dHA6Ly9mcmVlLWVsZWN0cm9ucy5jb20KCl9fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCmxpbnV4LWFybS1rZXJuZWwg
bWFpbGluZyBsaXN0CmxpbnV4LWFybS1rZXJuZWxAbGlzdHMuaW5mcmFkZWFkLm9yZwpodHRwOi8v
bGlzdHMuaW5mcmFkZWFkLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2xpbnV4LWFybS1rZXJuZWwK
next prev parent reply other threads:[~2017-01-11 19:40 UTC|newest]
Thread overview: 16+ 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 [this message]
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
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
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=2706391484163632@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