From: Rajendra Nayak <rnayak@ti.com>
To: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org
Cc: tony@atomide.com, bcousson@baylibre.com, Rajendra Nayak <rnayak@ti.com>
Subject: [PATCH 1/3] Documentation: dts: OMAP: Fix typos in DRA752 device name
Date: Fri, 14 Mar 2014 14:50:39 +0530 [thread overview]
Message-ID: <1394788841-15112-2-git-send-email-rnayak@ti.com> (raw)
In-Reply-To: <1394788841-15112-1-git-send-email-rnayak@ti.com>
DRA752 device is wrongly documented as DRA742 device. Fix the typo.
Signed-off-by: Rajendra Nayak <rnayak@ti.com>
---
.../devicetree/bindings/arm/omap/omap.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/arm/omap/omap.txt b/Documentation/devicetree/bindings/arm/omap/omap.txt
index af9b4a0..0491868 100644
--- a/Documentation/devicetree/bindings/arm/omap/omap.txt
+++ b/Documentation/devicetree/bindings/arm/omap/omap.txt
@@ -48,7 +48,7 @@ SoC Families:
compatible = "ti,omap4"
- OMAP5 generic - defaults to OMAP5430
compatible = "ti,omap5"
-- DRA7 generic - defaults to DRA742
+- DRA7 generic - defaults to DRA752
compatible = "ti,dra7"
- AM43x generic - defaults to AM4372
compatible = "ti,am43"
@@ -79,7 +79,7 @@ SoCs:
- OMAP5432
compatible = "ti,omap5432", "ti,omap5"
-- DRA742
+- DRA752
compatible = "ti,dra7xx", "ti,dra7"
- AM4372
--
1.7.9.5
next prev parent reply other threads:[~2014-03-14 9:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 9:20 [PATCH 0/3] ARM: DRA7: Add support for DRA72x devices Rajendra Nayak
2014-03-14 9:20 ` Rajendra Nayak [this message]
2014-04-23 8:39 ` [PATCH 1/3] Documentation: dts: OMAP: Fix typos in DRA752 device name Rajendra Nayak
2014-03-14 9:20 ` [PATCH 2/3] arm: dts: Add support for DRA72x family of devices Rajendra Nayak
2014-03-14 9:20 ` [PATCH 3/3] ARM: OMAP2+: Add machine entry for dra72x devices Rajendra Nayak
2014-03-15 2:21 ` Suman Anna
2014-03-18 4:43 ` Rajendra Nayak
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=1394788841-15112-2-git-send-email-rnayak@ti.com \
--to=rnayak@ti.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.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).