[P350] Build QUOTA2

Change-Id: I8c66bcafda1d5dd87f35223964d0e9f19a03f62f
Signed-off-by: RonGokhale <cips173@gmail.com>
Upgrade ipv6 interface

Change-Id: Id363e559a91d2f309333db81b08a59002ede9afd
Signed-off-by: RonGokhale <cips173@gmail.com>
SCRIPT: WE USE IT -j128
Update build.sh
jenkins test
we build this kernel on local pc too

This reverts commit e1128cea923112018ec1671c46602e8909902dd0.
ZRAM: Backport google's SNAPPY

Change-Id: I3d84e97fdb22a0a0ae91b3fdd3e510fe46a77c74
Signed-off-by: RonGokhale <cips173@gmail.com>
Staging: Backport zcache from .37

Change-Id: Ie8e9615c39acd6d159899ab189f2b127c00e0996
Signed-off-by: RonGokhale <cips173@gmail.com>
[P350] Updated defconfig

Change-Id: I3411eb656f9a6b1d32e1e49abe13b1e2ae4d6c42
Signed-off-by: RonGokhale <cips173@gmail.com>
mm : add lowmem detection logic

Final purpose of this patch is for improving oom/memoy shortage
detection
better. In general there are OOM cases that lowmem is exhausted. What
this lowmem means is determined by the situation, but in general,
limited amount of memory for some special use is lowmem.

This patch adds an integer lowmem_zone, which is initialized to -1.
If zone_idx(zone) <= lowmem_zone, the zone is lowmem.

This patch uses simple definition that the zone for special use is the
lowmem.
Not taking the amount of memory into account.

For example,
- if HIGHMEM is used, NORMAL is lowmem.
- If the system has both of NORMAL and DMA32, DMA32 is lowmem.
- When the system consists of only one zone, there are no lowmem.

This will be used for lowmem accounting per mm_struct and its
information
will be used for oom-killer.

Q: Why you don't use policy_zone ?
A: It's for NUMA only. I want to use unified approach for detecting
lowmem.
And policy_zone sounds like "for mempolicy"..

Concerns or TODO:
- Now, we have polizy_zone if CONFIG_NUMA=y. Maybe we can make it as
or remove it. But this itself should be done in other patch.

Changelog: 2009/12/14
- no change.
Changelog: 2009/12/09
- stop using policy_zone and use unified definition on each config.

Reviewed-by: Minchan Kim <minchan.kim@gmail.com>
Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Revert "mm : add lowmem detection logic"

This reverts commit c83efb100b9f5889d23f6915c7c782794f818f61.
build.sh: Show building time

Change-Id: I4994cbc09e908d4ce2741f568acc59b816f63792
Signed-off-by: RonGokhale <cips173@gmail.com>
build.sh: Make output of zip more uniform.

Change-Id: Iace8f4b672ac946d2448b25edab372a8b8f4d842
Signed-off-by: RonGokhale <cips173@gmail.com>
build.sh: fix localversion for cm9/10

Change-Id: Ia8052f92c055181662687c41bb0de8167c61d90f
Signed-off-by: RonGokhale <cips173@gmail.com>
drivers: input: Adding mcs8000 from l5 source

This is WIP

Change-Id: I97bfdb7ab1e416bdb8581e8b1d61f8517263f68b
Signed-off-by: RonGokhale <cips173@gmail.com>
Add missing header, fix mcs800 build

Change-Id: I6d52f72357182cb3891c3a0e9a4b6590181e7e6f
input: mt: add the ABS_MT_PRESSURE event

For pressure-based multi-touch devices, a direct way to send sensor
intensity data per finger is needed. This patch adds the ABS_MT_PRESSURE
event to the MT protocol.

Requested-by: Yoonyoung Shim <jy0922.shim@xxxxxxxxxxx>
Requested-by: Mika Kuoppala <mika.kuoppala@xxxxxxxxx>
Requested-by: Peter Hutterer <peter.hutterer@xxxxxxxxx>
Signed-off-by: Henrik Rydberg <rydberg@xxxxxxxxxxx>
power: Backport kernel/power from 2.6.35

Change-Id: If58c229b4d4a766c1634a2d3d4239bddd8560448
Signed-off-by: RonGokhale <cips173@gmail.com>
PM: Backport from 2.6.35

Change-Id: I6db133aee99a60003803a98f8c6b38050a3c4913
Signed-off-by: RonGokhale <cips173@gmail.com>
base: genlock: Properly destroy handle resources

The resources allocated for a handle were not being freed on device
release.  This included releasing the lock.  Unfortunately, the
lock release had a fput() too many which was screwing up the
reference counting on the file descriptors.  When attaching a lock,
we only need the file pointer for a short time so fput() it back
immediately.  That way, only there will only be one reference to
the lock per process, and the process will be responsible for
closing the fd directly and the fput() in genlock_release_lock
is no longer needed.

CRs-fixed: 322645
Change-Id: Ic0dedbad55300a2f8463c800cf8361719583b0b8
Signed-off-by: Jordan Crouse <jcrouse@codeaurora.org>