From: Matt Porter <mporter-l0cyMroinI0@public.gmane.org>
To: Linux OMAP List <linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: Devicetree Discuss
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
Linux Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Linux ARM Kernel List
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: [PATCH v2 0/2] ARM: dts: AM33xx: Correct gpio labels to match docs
Date: Mon, 10 Sep 2012 15:45:10 -0400 [thread overview]
Message-ID: <1347306312-31533-1-git-send-email-mporter@ti.com> (raw)
Changes since v1:
- Series now applies on top of Anil's AM33XX DTS series
This series applies on top of the for_3.7/dts/ branch and Anil's
"[v7,2/3] arm/dts: AM33XX: Configure pinmuxs for user leds control on Bone"
patch that is part of the overall series adding led and pinctrl DTS data
for AM33xx.
It is intended to correct the current labeling of gpios in the DTS before
too many more drivers are submitted for AM33xx that have gpios not matching
the docs.
Matt Porter (2):
ARM: dts: AM33XX: fix gpio node numbering to match hardware
ARM: dts: AM33XX: adjust leds to use the corrected gpio label
arch/arm/boot/dts/am335x-bone.dts | 8 ++++----
arch/arm/boot/dts/am33xx.dtsi | 8 ++++----
2 files changed, 8 insertions(+), 8 deletions(-)
--
1.7.9.5
next reply other threads:[~2012-09-10 19:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 19:45 Matt Porter [this message]
[not found] ` <1347306312-31533-1-git-send-email-mporter-l0cyMroinI0@public.gmane.org>
2012-09-10 19:45 ` [PATCH v2 1/2] ARM: dts: AM33XX: fix gpio node numbering to match hardware Matt Porter
2012-09-11 6:38 ` [PATCH v2 0/2] ARM: dts: AM33xx: Correct gpio labels to match docs Hiremath, Vaibhav
2012-09-10 19:45 ` [PATCH v2 2/2] ARM: dts: AM33XX: adjust leds to use the corrected gpio label Matt Porter
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=1347306312-31533-1-git-send-email-mporter@ti.com \
--to=mporter-l0cymroini0@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).