From: James Pettigrew <james-Rly9TSIBl47vnOemgxGiVw@public.gmane.org>
To: maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
mark.rutland-5wv7dgnIgG8@public.gmane.org,
linux-I+IVW8TIWO2tmTQ+vhA3Yw@public.gmane.org,
wens-jdAy2FN1RRM@public.gmane.org
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org,
james-Rly9TSIBl47vnOemgxGiVw@public.gmane.org
Subject: [PATCH v4 0/2] ARM: sunxi: Add support for FriendlyARM NanoPi NEO SBC
Date: Tue, 6 Sep 2016 08:15:55 +1000 [thread overview]
Message-ID: <cover.1473112593.git.james@innovum.com.au> (raw)
In-Reply-To: <1472701734-1837-1-git-send-email-james-Rly9TSIBl47vnOemgxGiVw@public.gmane.org>
Changes in v2:
As per Rask's review (thank you):
Added vendor prefix
Removed unncessary input.h include
Fixed underscores and unnecessary unit addresses in node names
Added GPIO pin comments to led nodes
Changes in v3:
Fixed syntax errors
Changes in v4:
Moved change to vendor-prefixes into separate patch
James Pettigrew (2):
ARM: dts: sun8i: Add dts file for the NanoPi NEO SBC
devicetree: Add vendor prefix for FriendlyARM
.../devicetree/bindings/vendor-prefixes.txt | 1 +
arch/arm/boot/dts/Makefile | 1 +
arch/arm/boot/dts/sun8i-h3-nanopi-neo.dts | 125 +++++++++++++++++++++
3 files changed, 127 insertions(+)
create mode 100644 arch/arm/boot/dts/sun8i-h3-nanopi-neo.dts
--
1.9.1
next prev parent reply other threads:[~2016-09-05 22:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 3:48 [PATCH 1/1] ARM: dts: sun8i: Add dts file for the NanoPi NEO SBC james
[not found] ` <1472701734-1837-1-git-send-email-james-Rly9TSIBl47vnOemgxGiVw@public.gmane.org>
2016-09-04 20:13 ` Rask Ingemann Lambertsen
2016-09-05 22:15 ` James Pettigrew [this message]
[not found] ` <cover.1473112593.git.james-Rly9TSIBl47vnOemgxGiVw@public.gmane.org>
2016-09-05 22:15 ` [PATCH v4 1/2] " James Pettigrew
2016-09-05 22:15 ` [PATCH v4 2/2] devicetree: Add vendor prefix for FriendlyARM James Pettigrew
[not found] ` <eb935b967af437ed40b7efe9e4e3d7bf6fd93724.1473112593.git.james-Rly9TSIBl47vnOemgxGiVw@public.gmane.org>
2016-09-06 2:41 ` Chen-Yu Tsai
2016-09-06 6:41 ` [PATCH v4 0/2] ARM: sunxi: Add support for FriendlyARM NanoPi NEO SBC Maxime Ripard
2016-09-05 0:42 ` [PATCH v2] ARM: dts: sun8i: Add dts file for the " James Pettigrew
[not found] ` <1473036168-20933-1-git-send-email-james-Rly9TSIBl47vnOemgxGiVw@public.gmane.org>
2016-09-05 2:35 ` kbuild test robot
2016-09-05 4:31 ` [PATCH v3] " James Pettigrew
[not found] ` <1473049907-17540-1-git-send-email-james-Rly9TSIBl47vnOemgxGiVw@public.gmane.org>
2016-09-05 12:06 ` Maxime Ripard
2016-09-05 18:31 ` Rask Ingemann Lambertsen
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=cover.1473112593.git.james@innovum.com.au \
--to=james-rly9tsibl47vnoemgxgivw@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-I+IVW8TIWO2tmTQ+vhA3Yw@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=wens-jdAy2FN1RRM@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).