From: Marek Belisko <marek@goldelico.com>
To: robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
linux@arm.linux.org.uk, bcousson@baylibre.com, tony@atomide.com
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
hns@goldelico.com, Marek Belisko <marek@goldelico.com>
Subject: [PATCH 0/3] arm: dts: omap3-gta04: Move common parts to include file and add models
Date: Mon, 28 Jul 2014 21:53:30 +0200 [thread overview]
Message-ID: <1406577213-9642-1-git-send-email-marek@goldelico.com> (raw)
This small patchset move omap3-gta04.dts to omap3-gta04.dtsi which then share
common parts with a3,a4 and a5 models. Models a3 and a5 have only small additions
to gta04a4 model.
Marek Belisko (3):
arm: dts: omap3-gta04: Rename gta04.dts to gta04.dtsi and add a4 model
arm: dts: Add gta04a3 model
arm: dts: Add gta04a5 model
arch/arm/boot/dts/Makefile | 4 +-
.../boot/dts/{omap3-gta04.dts => omap3-gta04.dtsi} | 0
arch/arm/boot/dts/omap3-gta04a3.dts | 48 ++++++++++++++++++++++
arch/arm/boot/dts/omap3-gta04a4.dts | 13 ++++++
arch/arm/boot/dts/omap3-gta04a5.dts | 17 ++++++++
5 files changed, 81 insertions(+), 1 deletion(-)
rename arch/arm/boot/dts/{omap3-gta04.dts => omap3-gta04.dtsi} (100%)
create mode 100644 arch/arm/boot/dts/omap3-gta04a3.dts
create mode 100644 arch/arm/boot/dts/omap3-gta04a4.dts
create mode 100644 arch/arm/boot/dts/omap3-gta04a5.dts
--
1.9.1
-
next reply other threads:[~2014-07-28 19:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 19:53 Marek Belisko [this message]
2014-07-28 19:53 ` [PATCH 1/3] arm: dts: omap3-gta04: Rename gta04.dts to gta04.dtsi and add a4 model Marek Belisko
2014-07-28 19:53 ` [PATCH 2/3] arm: dts: Add gta04a3 model Marek Belisko
2014-07-28 19:53 ` [PATCH 3/3] arm: dts: Add gta04a5 model Marek Belisko
2014-07-28 19:56 ` Michael Trimarchi
2014-07-28 20:02 ` Belisko Marek
2014-07-28 20:04 ` Michael Trimarchi
[not found] ` <CAOf5uw=Fm9FXEH5ESqDC8pGjMbn5VQ1+MyPJVXSqGh_9+JRLHw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-07-28 20:06 ` Belisko Marek
2014-07-28 20:12 ` Michael Trimarchi
[not found] ` <CAOf5uwmjznuK_1au1HnsnYh=BhqC=x+O_tpk6U71bqPv=hFe_A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-07-29 5:17 ` Dr. H. Nikolaus Schaller
2014-07-28 20:12 ` Dr. H. Nikolaus Schaller
2014-07-28 20:42 ` Dr. H. Nikolaus Schaller
[not found] ` <1FA8171E-1B7A-4684-887E-11593BB9C29E-xXXSsgcRVICgSpxsJD1C4w@public.gmane.org>
2014-07-29 12:41 ` Tony Lindgren
2014-07-29 13:03 ` Dr. H. Nikolaus Schaller
[not found] ` <589F7CA3-F245-4299-8E39-36A7FA9F3CBD-xXXSsgcRVICgSpxsJD1C4w@public.gmane.org>
2014-07-29 14:12 ` Javier Martinez Canillas
[not found] ` <CABxcv=n7g8c2ePGKgu_0Y35iearcRoAj9ZH5jDWY9nE+1uUKnA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-08-01 8:02 ` Tony Lindgren
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=1406577213-9642-1-git-send-email-marek@goldelico.com \
--to=marek@goldelico.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=hns@goldelico.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=tony@atomide.com \
/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).