From: Rask Ingemann Lambertsen <ccc94453@vip.cybercity.dk>
To: James Pettigrew <james@innovum.com.au>
Cc: maxime.ripard@free-electrons.com, robh+dt@kernel.org,
mark.rutland@arm.com, linux@armlinux.org.uk, wens@csie.org,
devicetree@vger.kernel.org, linux-sunxi@googlegroups.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3] ARM: dts: sun8i: Add dts file for the NanoPi NEO SBC
Date: Mon, 5 Sep 2016 20:31:21 +0200 [thread overview]
Message-ID: <20160905183121.54f4jrd7u7snugz6@x1-6-00-0f-9f-c6-3e-90.cpe.webspeed.dk> (raw)
In-Reply-To: <1473049907-17540-1-git-send-email-james@innovum.com.au>
On Mon, Sep 05, 2016 at 02:31:47PM +1000, James Pettigrew wrote:
> The NanoPi NEO is a minimal H3 based SBC. It comes with 256/512M RAM, a
> micro SD slot, 10/100Mbit ethernet and a single USB-A port.
>
> Signed-off-by: James Pettigrew <james@innovum.com.au>
Reviewed-by: Rask Ingemann Lambertsen <ccc94453@vip.cybercity.dk>
--
Rask Ingemann Lambertsen
next prev parent reply other threads:[~2016-09-05 18:31 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
2016-09-04 20:13 ` Rask Ingemann Lambertsen
2016-09-05 0:42 ` [PATCH v2] " James Pettigrew
2016-09-05 2:35 ` kbuild test robot
2016-09-05 4:31 ` [PATCH v3] " James Pettigrew
2016-09-05 12:06 ` Maxime Ripard
2016-09-05 18:31 ` Rask Ingemann Lambertsen [this message]
2016-09-05 22:15 ` [PATCH v4 0/2] ARM: sunxi: Add support for FriendlyARM " James Pettigrew
2016-09-05 22:15 ` [PATCH v4 1/2] ARM: dts: sun8i: Add dts file for the " James Pettigrew
2016-09-05 22:15 ` [PATCH v4 2/2] devicetree: Add vendor prefix for FriendlyARM James Pettigrew
2016-09-06 2:41 ` [linux-sunxi] " Chen-Yu Tsai
2016-09-06 6:41 ` [PATCH v4 0/2] ARM: sunxi: Add support for FriendlyARM NanoPi NEO SBC Maxime Ripard
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=20160905183121.54f4jrd7u7snugz6@x1-6-00-0f-9f-c6-3e-90.cpe.webspeed.dk \
--to=ccc94453@vip.cybercity.dk \
--cc=devicetree@vger.kernel.org \
--cc=james@innovum.com.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@free-electrons.com \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).