From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 0/3] Add ZTE ZX296718 support
Date: Tue, 13 Sep 2016 15:21:46 +0800 [thread overview]
Message-ID: <20160913072146.GA7398@tiger> (raw)
In-Reply-To: <1473730926-1034-1-git-send-email-jun.nie@linaro.org>
On Tue, Sep 13, 2016 at 09:42:03AM +0800, Jun Nie wrote:
> Changes in version5:
> - Add GPL license to new files.
> - Unify clocks dts nodes names.
> - Move interrupt parents info to root nodes in dts, move
> pmu and timer node out of soc node.
>
> Changes in version4:
> - Change dts file name to align with compatible name.
> - Reorder dts nodes with reg address sequence.
> - Move nodes out of soc, which do not have soc simple
> bus address or share soc interrupt.
> - Change some nodes name to align with convention.
>
> Changes in version3:
> - Remove unnecessary flag of gic in dts.
>
> Changes in version2:
> - Use more precise cpu and pmu compatible name in dts.
> - fix minor coding style issue.
>
>
> Jun Nie (3):
> arm64: add ZTE ZX SoC family
> arm64: dts: Add ZTE ZX296718 SoC dts and Makefile
> arm64: defconfig: enable ZTE ZX related config
For the series,
Reviewed-by: Shawn Guo <shawnguo@kernel.org>
Arnd, Olof,
If you like, I can help collect ZTE DTS patches to reduce your
maintenance burden, considering we have an established pull-request
work flow and I get ZTE platform on hands to test patches.
Shawn
next prev parent reply other threads:[~2016-09-13 7:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 1:42 [PATCH v5 0/3] Add ZTE ZX296718 support Jun Nie
2016-09-13 1:42 ` [PATCH v5 1/3] arm64: add ZTE ZX SoC family Jun Nie
2016-09-13 1:42 ` [PATCH v5 2/3] arm64: dts: Add ZTE ZX296718 SoC dts and Makefile Jun Nie
2016-09-16 2:55 ` Shawn Guo
2016-09-13 1:42 ` [PATCH v5 3/3] arm64: defconfig: enable ZTE ZX related config Jun Nie
2016-09-13 7:21 ` Shawn Guo [this message]
2016-09-15 13:24 ` [PATCH v5 0/3] Add ZTE ZX296718 support Arnd Bergmann
2016-09-16 6:38 ` Shawn Guo
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=20160913072146.GA7398@tiger \
--to=shawnguo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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 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.