From: Olof Johansson <olof@lixom.net>
To: torvalds@linux-foundation.org
Cc: linux-arm-kernel@lists.infradead.org, arm@kernel.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] ARM: SoC fixes for 3.7
Date: Wed, 21 Nov 2012 15:28:54 -0800 [thread overview]
Message-ID: <20121121232854.GB18134@quad.lixom.net> (raw)
Hi Linus,
The following changes since commit f4a75d2eb7b1e2206094b901be09adb31ba63681:
Linux 3.7-rc6 (2012-11-16 17:42:40 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git tags/fixes-for-linus
for you to fetch changes up to 65546ab097b023886a60df4cbc931d4cc362b98e:
Merge tag 'omap-for-v3.7-rc5/fixes-signed' of git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap into fixes (2012-11-21 13:56:36 -0800)
----------------------------------------------------------------
ARM: SoC fixes for 3.7
A few more fixes for final 3.7. Two dealing with pinmux setup on OMAP, and
one dealing with TV output on DaVinci. And one small MAINTAINER update.
----------------------------------------------------------------
Anders Hedlund (1):
ARM: OMAP3: igep0020: Set WIFI/BT GPIO pins in correct mux mode
Javier Martinez Canillas (1):
ARM: OMAP: Add maintainer entry for IGEP machines
Kevin Hilman (1):
ARM: OMAP4: TWL: mux sys_drm_msecure as output for PMIC
Lad, Prabhakar (1):
ARM: davinci: dm644x: fix out range signal for ED
Olof Johansson (2):
Merge tag 'davinci-fixes-for-v3.7' of git://gitorious.org/linux-davinci/linux-davinci into fixes
Merge tag 'omap-for-v3.7-rc5/fixes-signed' of git://git.kernel.org/.../tmlind/linux-omap into fixes
MAINTAINERS | 8 ++++++++
arch/arm/mach-davinci/dm644x.c | 3 +--
arch/arm/mach-omap2/board-igep0020.c | 5 +++++
arch/arm/mach-omap2/twl-common.c | 1 +
4 files changed, 15 insertions(+), 2 deletions(-)
reply other threads:[~2012-11-22 18:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20121121232854.GB18134@quad.lixom.net \
--to=olof@lixom.net \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).