From: Tony Lindgren <tony@atomide.com>
To: Suman Anna <s-anna@ti.com>
Cc: Benoit Cousson <bcousson@baylibre.com>,
Mark Rutland <mark.rutland@arm.com>,
Ohad Ben-Cohen <ohad@wizery.com>,
devicetree@vger.kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] OMAP hwspinlock DT updates
Date: Fri, 28 Feb 2014 14:14:39 -0800 [thread overview]
Message-ID: <20140228221439.GI13624@atomide.com> (raw)
In-Reply-To: <1389659207-39445-1-git-send-email-s-anna@ti.com>
* Suman Anna <s-anna@ti.com> [140113 16:29]:
> Hi,
>
> This series updates the existing OMAP hwspinlock DT nodes to have a
> #hwlock-cells property as suggested by Mark Rutland [1], and adds the
> hwspinlock nodes for two other newer SoCs - DRA7xx and AM43xx.
>
> Posting the series separately from the driver DT adapation changes [2]
> to avoid maintainer confusion.
Thanks applying into omap-for-v3.15/dt.
Tony
> [1] http://marc.info/?l=linux-omap&m=138433541420926&w=2
> [2] http://marc.info/?l=linux-omap&m=138965904015225&w=2
>
> Suman Anna (3):
> ARM: dts: OMAP: Add #hwlock-cells property to hwspinlock nodes
> ARM: dts: DRA7: Add hwspinlock node
> ARM: dts: AM4372: Add hwspinlock node
>
> arch/arm/boot/dts/am33xx.dtsi | 1 +
> arch/arm/boot/dts/am4372.dtsi | 7 +++++++
> arch/arm/boot/dts/dra7.dtsi | 7 +++++++
> arch/arm/boot/dts/omap4.dtsi | 1 +
> arch/arm/boot/dts/omap5.dtsi | 1 +
> 5 files changed, 17 insertions(+)
>
> --
> 1.8.4.3
>
prev parent reply other threads:[~2014-02-28 22:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 0:26 [PATCH 0/3] OMAP hwspinlock DT updates Suman Anna
2014-01-14 0:26 ` [PATCH 1/3] ARM: dts: OMAP: Add #hwlock-cells property to hwspinlock nodes Suman Anna
2014-01-14 0:26 ` [PATCH 2/3] ARM: dts: DRA7: Add hwspinlock node Suman Anna
2014-01-14 0:26 ` [PATCH 3/3] ARM: dts: AM4372: " Suman Anna
2014-02-28 22:14 ` Tony Lindgren [this message]
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=20140228221439.GI13624@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=ohad@wizery.com \
--cc=s-anna@ti.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).