From: Kishon Vijay Abraham I <kishon@ti.com>
To: <grant.likely@secretlab.ca>, <rob.herring@calxeda.com>,
<rob@landley.net>, <linux@arm.linux.org.uk>, <kishon@ti.com>,
<arnd@arndb.de>, <balbi@ti.com>, <b-cousson@ti.com>,
<tony@atomide.com>, <devicetree-discuss@lists.ozlabs.org>,
<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: [PATCH 0/2] ARM: dts: Add subnode for ocp2scp
Date: Wed, 19 Sep 2012 16:02:50 +0530 [thread overview]
Message-ID: <1348050772-27819-1-git-send-email-kishon@ti.com> (raw)
This patch series contains a patch to explicitly add reg property
to the ocp2scp dt node and a patch to add the subnode for ocp2scp
(omap-usb2).
Since the original patch series that adds ocp2scp driver and ocp2scp
data are merged in arm-soc, I'm sending this patch series based on the
same tree.
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git
But Benoit already pointed out that there's going to be merge conflicts
as he has sent a bunch of dt data patches to linux-omap (devel-dt) tree.
So now I'm not sure how that can be actually avoided.
Kishon Vijay Abraham I (2):
ARM: dts: omap4: add *reg* property for ocp2scp
ARM: dts: omap: Add omap-usb2 dt data
.../devicetree/bindings/bus/omap-ocp2scp.txt | 14 ++++++++++++++
arch/arm/boot/dts/omap4.dtsi | 8 +++++++-
2 files changed, 21 insertions(+), 1 deletion(-)
--
1.7.9.5
next reply other threads:[~2012-09-19 10:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 10:32 Kishon Vijay Abraham I [this message]
2012-09-19 10:32 ` [PATCH 1/2] ARM: dts: omap: add *reg* property for ocp2scp Kishon Vijay Abraham I
2012-09-19 10:32 ` [PATCH 2/2] ARM: dts: omap: Add omap-usb2 dt data Kishon Vijay Abraham I
2013-01-10 9:31 ` kishon
2013-01-10 10:04 ` Benoit Cousson
2013-01-10 10:16 ` kishon
2013-01-10 12:45 ` Felipe Balbi
2013-01-10 18:35 ` Tony Lindgren
2012-09-20 3:26 ` [PATCH 0/2] ARM: dts: Add subnode for ocp2scp Benoit Cousson
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=1348050772-27819-1-git-send-email-kishon@ti.com \
--to=kishon@ti.com \
--cc=arnd@arndb.de \
--cc=b-cousson@ti.com \
--cc=balbi@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--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).