From: Jagan Teki <jagan@openedev.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] sunxi: add proper device tree for Orange Pi Zero boards
Date: Tue, 20 Dec 2016 15:56:05 +0100 [thread overview]
Message-ID: <CAD6G_RQf2sUEdCmAsf+FN1W65uDo4mvbVQYV4fNh6ARXdYfBoA@mail.gmail.com> (raw)
In-Reply-To: <CAD6G_RTktD214R7Q15j3D74xpWJisE7Q2c9z-pBT0bS6djWaZQ@mail.gmail.com>
On Mon, Dec 19, 2016 at 6:20 PM, Jagan Teki <jagan@openedev.com> wrote:
> On Mon, Dec 19, 2016 at 5:23 PM, Icenowy Zheng <icenowy@aosc.xyz> wrote:
>>
>>
>> 16.12.2016, 22:52, "Jagan Teki" <jagan@openedev.com>:
>>> On Fri, Dec 16, 2016 at 3:35 PM, Icenowy Zheng <icenowy@aosc.xyz> wrote:
>>>> Add a proper device tree file for Orange Pi Zero boards from Xunlong,
>>>> which come with a Allwinner H2+ SoC (similar to H3).
>>>>
>>>> Signed-off-by: Icenowy Zheng <icenowy@aosc.xyz>
>>>
>>> Reviewed-by: Jagan Teki <jagan@openedev.com>
>>
>> Could you merge this patchset?
>>
>> As Hans de Goede said in
>> http://lists.denx.de/pipermail/u-boot/2016-December/276487.html ,
>> he's no longer the maintainer, and now the maintainer is you.
>
> Yes, I will apply for next.
Applied to u-boot-sunxi/next
thanks!
--
Jagan Teki
Free Software Engineer | www.openedev.com
U-Boot, Linux | Upstream Maintainer
Hyderabad, India.
prev parent reply other threads:[~2016-12-20 14:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-16 14:35 [U-Boot] [PATCH 1/2] sunxi: add proper device tree for Orange Pi Zero boards Icenowy Zheng
2016-12-16 14:35 ` [U-Boot] [PATCH 2/2] sunxi: add orangepi zero defconfig Icenowy Zheng
2016-12-16 14:52 ` Jagan Teki
2016-12-20 14:55 ` Jagan Teki
2016-12-16 14:51 ` [U-Boot] [PATCH 1/2] sunxi: add proper device tree for Orange Pi Zero boards Jagan Teki
2016-12-19 16:23 ` Icenowy Zheng
2016-12-19 17:20 ` Jagan Teki
2016-12-20 14:56 ` Jagan Teki [this message]
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=CAD6G_RQf2sUEdCmAsf+FN1W65uDo4mvbVQYV4fNh6ARXdYfBoA@mail.gmail.com \
--to=jagan@openedev.com \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.