From: John Stultz <john.stultz@linaro.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Android Kernel Team <kernel-team@android.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] staging: Android updates
Date: Wed, 07 Mar 2012 13:34:06 -0800 [thread overview]
Message-ID: <1331156046.2191.185.camel@work-vm> (raw)
Hi Greg,
Just wanted to send along some Android updates to the staging-next tree
so they can be queued for 3.4. I've pulled these from the
common/android-3.3 branch, and made only some minor changes to keep
everything in the staging dir and to avoid compile issues on x86.
The patches can be browsed over here:
http://git.linaro.org/gitweb?p=people/jstultz/android-dev.git;a=shortlog;h=refs/heads/dev/android-staging-updates
thanks
-john
The following changes since commit 1ec41a31fb695682cab7fc7c1f6ced84d188b6f9:
staging: ozwpan: remove debug allocator (2012-03-02 16:51:09 -0800)
are available in the git repository at:
git://git.linaro.org/people/jstultz/android-dev.git dev/android-staging-updates
Colin Cross (11):
android: binder: fix warning
android: ram_console: move footer strings
android: ram_console: drop early buffer support
android: ram_console: drop verbose ram_console support
android: ram_console: split out persistent ram
android: persistent_ram: refactor ecc support
android: persistent_ram: handle reserving and mapping memory
android: persistent_ram: make persistent_ram_write atomic
android: persistent_ram: add notrace to persistent_ram_write
android: persistent_trace: ftrace into persistent_ram
android: staging: ram_console: fix crash in ram_console_late_init
Dima Zavin (1):
android: ram_console: set CON_ANYTIME console flag
John Stultz (1):
android: lowmemorykiller: Fix warning on 64bit
Nick Kralevich (1):
android: ram_console: honor dmesg_restrict
drivers/staging/android/Kconfig | 70 +---
drivers/staging/android/Makefile | 4 +
drivers/staging/android/binder.c | 2 +-
drivers/staging/android/lowmemorykiller.c | 2 +-
drivers/staging/android/persistent_ram.c | 470 ++++++++++++++++++++++++++++
drivers/staging/android/persistent_ram.h | 78 +++++
drivers/staging/android/ram_console.c | 412 +++++--------------------
drivers/staging/android/trace_persistent.c | 242 ++++++++++++++
8 files changed, 888 insertions(+), 392 deletions(-)
create mode 100644 drivers/staging/android/persistent_ram.c
create mode 100644 drivers/staging/android/persistent_ram.h
create mode 100644 drivers/staging/android/trace_persistent.c
next reply other threads:[~2012-03-07 21:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 21:34 John Stultz [this message]
2012-03-07 21:42 ` [GIT PULL] staging: Android updates Greg KH
2012-03-07 21:52 ` John Stultz
2012-03-07 21:46 ` 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=1331156046.2191.185.camel@work-vm \
--to=john.stultz@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.