From: Jon Hunter <jon-hunter@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
device-tree <devicetree-discuss@lists.ozlabs.org>
Subject: [GIT PULL] ARM: OMAP2+: GPMC fixes for v3.10
Date: Tue, 30 Apr 2013 08:53:52 -0500 [thread overview]
Message-ID: <517FCCF0.1030105@ti.com> (raw)
The following changes since commit aecb65a34a780cd07fbaa652cc5d640f13f3ed5f:
Merge branch 'omap-gpmc-for-v3.10-take2' of git://github.com/jonhunter/linux into omap-for-v3.10/gpmc (2013-04-04 11:22:33 -0700)
are available in the git repository at:
git://github.com/jonhunter/linux.git omap-gpmc-fixes-for-v3.10
for you to fetch changes up to b327b3627bb428eb7d98f25224532425a673d89e:
ARM: OMAP2+: only WARN if a GPMC child probe function fail (2013-04-30 08:43:05 -0500)
----------------------------------------------------------------
GPMC fixes for v3.10. Main fix is to only search the GPMC node
for GPMC child devices and not the entire device-tree (which was
breaking ethernet support on some boards where the GPMC does not
interface with the ethernet chip). This branch is based upon
Tony's omap-for-v3.10/gpmc branch.
----------------------------------------------------------------
Javier Martinez Canillas (3):
Documentation: dt: update TI GPMC ethernet binding properties
ARM: OMAP2+: only search for GPMC DT child nodes on probe
ARM: OMAP2+: only WARN if a GPMC child probe function fail
Jon Hunter (1):
Documentation: dt: update properties in TI GPMC NAND example
.../devicetree/bindings/mtd/gpmc-nand.txt | 28 +++++-----
Documentation/devicetree/bindings/net/gpmc-eth.txt | 56 ++++++++++----------
arch/arm/mach-omap2/gpmc.c | 38 +++++--------
3 files changed, 54 insertions(+), 68 deletions(-)
next reply other threads:[~2013-04-30 13:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 13:53 Jon Hunter [this message]
2013-05-09 0:13 ` [GIT PULL] ARM: OMAP2+: GPMC fixes for v3.10 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=517FCCF0.1030105@ti.com \
--to=jon-hunter@ti.com \
--cc=devicetree-discuss@lists.ozlabs.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).