linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@bootlin.com>
To: Jagan Teki <jagan@amarulasolutions.com>
Cc: Chen-Yu Tsai <wens@csie.org>, Icenowy Zheng <icenowy@aosc.io>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-sunxi@googlegroups.com,
	Jagan Teki <jagan@openedev.com>
Subject: Re: [PATCH v2 3/3] arm64: allwinner: h6: Add OrangePi Lite2 initial support
Date: Mon, 5 Nov 2018 16:23:03 +0100	[thread overview]
Message-ID: <20181105152303.pcpq4btw5ecwzs2y@flea> (raw)
In-Reply-To: <20181105074842.21988-3-jagan@amarulasolutions.com>

[-- Attachment #1: Type: text/plain, Size: 569 bytes --]

On Mon, Nov 05, 2018 at 01:18:42PM +0530, Jagan Teki wrote:
> From: Jagan Teki <jagan@openedev.com>
> 
> OrangePi Lite2 is Allwinner H6 based open-source SBC,
> which support:
> - Allwinner H6 Quad-core 64-bit ARM Cortex-A53
> - GPU Mali-T720
> - 1GB LPDDR3 RAM
> - AXP805 PMIC
> - AP6356S Wifi/BT
> - USB 2.0, USB 3.0 Host, OTG
> - HDMI port
> - 5V/2A DC power supply
> 
> Signed-off-by: Jagan Teki <jagan@openedev.com>

Applied patch 2 and 3, thanks!
Maxime

-- 
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2018-11-05 15:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-05  7:48 [PATCH v2 1/3] clk: sunxi-ng: sun50i: h6: Fix MMC clock mux width Jagan Teki
2018-11-05  7:48 ` [PATCH v2 2/3] arm64: allwinner: h6: Add common orangepi nodes into dtsi Jagan Teki
2018-11-05  7:48 ` [PATCH v2 3/3] arm64: allwinner: h6: Add OrangePi Lite2 initial support Jagan Teki
2018-11-05 15:23   ` Maxime Ripard [this message]
2018-11-05 16:11 ` [PATCH v2 1/3] clk: sunxi-ng: sun50i: h6: Fix MMC clock mux width Chen-Yu Tsai

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=20181105152303.pcpq4btw5ecwzs2y@flea \
    --to=maxime.ripard@bootlin.com \
    --cc=devicetree@vger.kernel.org \
    --cc=icenowy@aosc.io \
    --cc=jagan@amarulasolutions.com \
    --cc=jagan@openedev.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@googlegroups.com \
    --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).