From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] non-urgent omap fixes for v3.17 merge window
Date: Thu, 24 Jul 2014 04:51:41 -0700 [thread overview]
Message-ID: <20140724115140.GB29045@atomide.com> (raw)
The following changes since commit cd3de83f147601356395b57a8673e9c5ff1e59d1:
Linux 3.16-rc4 (2014-07-06 12:37:51 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v3.17/fixes-not-urgent-signed
for you to fetch changes up to 00e4e5b5b0339bde4b0ecb23d7d7969a3bebd44d:
Merge remote-tracking branch 'roger/for-v3.17/gpmc-omap' into omap-for-v3.17/fixes-not-urgent (2014-07-15 00:24:39 -0700)
----------------------------------------------------------------
Fixes for omaps that were not considered urgent enough for the
rc series. Mostly a fix for GPMC allocation and omap5 ABB
(Adaptive Body Bias).
----------------------------------------------------------------
Andrii.Tseglytskyi (1):
ARM: dts: OMAP5: Add device nodes for ABB
Nicholas Krause (1):
omap16xx: Removes fixme no longer needed in ocpi_enable()
Rickard Strandqvist (1):
ARM: omap2+: usb-tusb6010.c: Cleaning up variable is set more than once
Rostislav Lisovy (1):
ARM: omap2+: gpmc-nand: Use dynamic platform_device_alloc()
Tony Lindgren (1):
Merge remote-tracking branch 'roger/for-v3.17/gpmc-omap' into omap-for-v3.17/fixes-not-urgent
arch/arm/boot/dts/omap5.dtsi | 60 +++++++++++++++++++++++++++++
arch/arm/mach-omap1/ocpi.c | 1 -
arch/arm/mach-omap2/gpmc-nand.c | 79 ++++++++++++++++++--------------------
arch/arm/mach-omap2/usb-tusb6010.c | 1 -
4 files changed, 97 insertions(+), 44 deletions(-)
next reply other threads:[~2014-07-24 11:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 11:51 Tony Lindgren [this message]
2014-07-26 9:36 ` [GIT PULL] non-urgent omap fixes for v3.17 merge window Arnd Bergmann
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=20140724115140.GB29045@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.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).