devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Maxime Ripard <maxime.ripard@free-electrons.com>,
	Icenowy Zheng <icenowy@aosc.xyz>
Cc: devicetree@vger.kernel.org,
	Vishnu Patekar <vishnupatekar0510@gmail.com>,
	Arnd Bergmann <arnd@arndb.de>,
	linux-doc@vger.kernel.org,
	Andre Przywara <andre.przywara@arm.com>,
	linux-sunxi@googlegroups.com,
	Russell King <linux@armlinux.org.uk>,
	linux-kernel@vger.kernel.org, Hans de Goede <hdegoede@redhat.com>,
	Chen-Yu Tsai <wens@csie.org>, Rob Herring <robh+dt@kernel.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 -next 1/2] ARM: sunxi: add support for H2+ SoC
Date: Tue, 6 Dec 2016 13:01:56 +1100	[thread overview]
Message-ID: <4c0bd9ab-05c7-bf53-e55a-fc4c108a456f@ozlabs.ru> (raw)
In-Reply-To: <20161205091955.zkffyktw5trfocnx@lukather>


[-- Attachment #1.1.1: Type: text/plain, Size: 504 bytes --]

On 05/12/16 20:19, Maxime Ripard wrote:
> On Fri, Dec 02, 2016 at 11:05:12PM +0800, Icenowy Zheng wrote:
>> Allwinner H2+ is a quad-core Cortex-A7 SoC.
>>
>> It is very like H3, that they share the same SoC ID (0x1680), and H3
>> memory maps as well as drivers works well on the SoC.
>>
>> Signed-off-by: Icenowy Zheng <icenowy@aosc.xyz>
> 
> Fixed the alphabetical order in the bindings doc, and applied.

Where is that resulting tree, with these ones and EMAC? Thanks.



-- 
Alexey


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 839 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2016-12-06  2:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-02 15:05 [PATCH v3 -next 1/2] ARM: sunxi: add support for H2+ SoC Icenowy Zheng
     [not found] ` <20161202150513.34691-1-icenowy-ymACFijhrKM@public.gmane.org>
2016-12-02 15:05   ` [PATCH v3 -next 2/2] ARM: dts: sunxi: add support for Orange Pi Zero board Icenowy Zheng
     [not found]     ` <20161202150513.34691-2-icenowy-ymACFijhrKM@public.gmane.org>
2016-12-02 16:41       ` Chen-Yu Tsai
     [not found]         ` <CAGb2v661hBsd7tBcYByeRKEZh+8YMB3ewbnkrT3rUvzP2f90yQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-12-03  9:43           ` Jernej Skrabec
2016-12-04  8:12         ` [linux-sunxi] " Alexey Kardashevskiy
2016-12-09  8:17       ` Maxime Ripard
2016-12-06  1:51     ` Alexey Kardashevskiy
2016-12-05  9:19   ` [PATCH v3 -next 1/2] ARM: sunxi: add support for H2+ SoC Maxime Ripard
2016-12-06  2:01     ` Alexey Kardashevskiy [this message]
2016-12-05  2:27 ` Alexey Kardashevskiy
  -- strict thread matches above, loose matches on Subject: below --
2016-12-05  6:44 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=4c0bd9ab-05c7-bf53-e55a-fc4c108a456f@ozlabs.ru \
    --to=aik@ozlabs.ru \
    --cc=andre.przywara@arm.com \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=hdegoede@redhat.com \
    --cc=icenowy@aosc.xyz \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@googlegroups.com \
    --cc=linux@armlinux.org.uk \
    --cc=maxime.ripard@free-electrons.com \
    --cc=robh+dt@kernel.org \
    --cc=vishnupatekar0510@gmail.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).