From: Daniel Walker <dwalker@codeaurora.org>
To: Russell King <linux@arm.linux.org.uk>
Cc: linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org,
Daniel Walker <dwalker@codeaurora.org>
Subject: [GIT PULL] ARM MSM for 2.6.36
Date: Tue, 15 Jun 2010 11:27:23 -0700 [thread overview]
Message-ID: <1276626445-20316-1-git-send-email-dwalker@codeaurora.org> (raw)
Russell,
Here are some patch that's have been submitted here a few times for review,
and recently have seen any comments. One fixes a memory defect seen on
our MSM7x30 platform, and the other enabled gpiolib for MSM and trout
specifically.
Anyway, Please pull and let me know if there's any issues.
Daniel
The following changes since commit 7e27d6e778cd87b6f2415515d7127eba53fe5d02:
Linux 2.6.35-rc3 (2010-06-11 19:14:04 -0700)
are available in the git repository at:
git://codeaurora.org/quic/kernel/dwalker/linux-msm.git for-russell
Michael Bohan (1):
arm: mm: Don't free prohibited memmap entries
Pavel Machek (1):
Add GPIO support for HTC Dream.
arch/arm/Kconfig | 1 +
arch/arm/mach-msm/Makefile | 2 +-
arch/arm/mach-msm/board-trout-gpio.c | 112 +++++++++++++++++++++++
arch/arm/mach-msm/board-trout.h | 157 +++++++++++++++++++++++++++++++++
arch/arm/mach-msm/include/mach/gpio.h | 7 ++
arch/arm/mm/init.c | 19 ++--
6 files changed, 287 insertions(+), 11 deletions(-)
create mode 100644 arch/arm/mach-msm/board-trout-gpio.c
next reply other threads:[~2010-06-15 18:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-15 18:27 Daniel Walker [this message]
2010-06-15 18:27 ` [PATCH 1/2] Add GPIO support for HTC Dream Daniel Walker
2010-06-15 18:27 ` [PATCH 2/2] arm: mm: Don't free prohibited memmap entries Daniel Walker
2010-06-15 18:28 ` [GIT PULL] ARM MSM for 2.6.36 Daniel Walker
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=1276626445-20316-1-git-send-email-dwalker@codeaurora.org \
--to=dwalker@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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).