From: Neil Armstrong <narmstrong@baylibre.com>
To: carlo@caione.org, khilman@baylibre.com
Cc: Neil Armstrong <narmstrong@baylibre.com>,
linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: [RESEND PATCH 0/3] ARM64: dts: meson-gx: Cleanup for common nodes
Date: Mon, 13 Mar 2017 10:10:49 +0100 [thread overview]
Message-ID: <1489396252-28696-1-git-send-email-narmstrong@baylibre.com> (raw)
Since we know the GXBB and GXL/GXM share more hardware, we can safely move
the remaining peripheral nodes present in the GXBB dtsi to the common GX dtsi.
The following patches are small cleanups and helps to uniform the GX common
dtsi compatible scheme.
Changes since original v1 at [1]:
- Add back missing changelog on patches 1 and 3
[1] http://lkml.kernel.org/r/1489055948-10656-1-git-send-email-narmstrong@baylibre.com
Neil Armstrong (3):
ARM64: dts: meson-gx: Finally move common nodes to GX dtsi
ARM64: dts: meson-gx: empty line cleanup
ARM64: dts: meson-gx: Prepend GX generic compatible like other nodes
arch/arm64/boot/dts/amlogic/meson-gx.dtsi | 39 ++++++++++++++++++++------
arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi | 43 ++++++-----------------------
arch/arm64/boot/dts/amlogic/meson-gxl.dtsi | 8 ++++++
3 files changed, 47 insertions(+), 43 deletions(-)
--
1.9.1
next reply other threads:[~2017-03-13 9:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 9:10 Neil Armstrong [this message]
2017-03-13 9:10 ` [RESEND PATCH 1/3] ARM64: dts: meson-gx: Finally move common nodes to GX dtsi Neil Armstrong
2017-03-13 9:10 ` [RESEND PATCH 2/3] ARM64: dts: meson-gx: empty line cleanup Neil Armstrong
2017-03-13 9:10 ` [RESEND PATCH 3/3] ARM64: dts: meson-gx: Prepend GX generic compatible like other nodes Neil Armstrong
2017-03-23 19:28 ` [RESEND PATCH 0/3] ARM64: dts: meson-gx: Cleanup for common nodes Kevin Hilman
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=1489396252-28696-1-git-send-email-narmstrong@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=carlo@caione.org \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®