config: support oom_adj values

See https://github.com/android/kernel_common/commit/77a6bf41d0d230ce0b2bfca58ddbea6e954fe950
Revert "fs: Remove missed ->fds_bits from cessation use of fd_set structs internally"

This reverts commit e7d8522d2ab91f6a505e0ad2b7345cbdff4775a1.

Reverting because this commit fixes/references a 3.4 kernel commit (1fd36ad)
which does not exits in 3.0.
Revert "Wrap accesses to the fd_sets in struct fdtable"

This reverts commit b8788928d8ab7ff317979883aac2eca01ff66d62.

Reverting because this commit is not needed for the 3.4 android binder to work.
cpufreq: interactive: sync android-3.0 with android-3.4

Change-Id: I71443db4edbe43a08fe58a54a742b4c788ef11e3
Signed-off-by: Todd Poynor <toddpoynor@google.com>

Conflicts:
	drivers/cpufreq/cpufreq_interactive.c
Revert "cpufreq: interactive: sync android-3.0 with android-3.4"

This reverts commit 75a8cb8204445968c511d3755113f5326a5f4507.
Merge branch 'cm-10.1-dev' into cm-10.1-wip
android: lowmemorykiller: modify return values to avoid extra calls

If the shrinker returns a large cache size, it will get called
repeatedly, proportional to the cache size divided by 128.  If
no processes to kill were found on the last pass through the
shrinker, there is no reason calling it again immediately will
find a process to kill.

Avoid the extra calls to the shrinker by:
Returning 0 when the shrinker is called with 0 and there are plenty
of free or file pages.  Avoids calling the shrinker at all during
this pass.
Returning rem when a thread is already dying.  Avoids telling the
shrinker core that the lowmemorykiller is making immense amounts
of forward progress.
Returning -1 when no process was selected for death.  Avoids calling
the shrinker again when nothing has changed.

Change-Id: I08f06063084f6070e71ac6afa7b14377149f3685
Signed-off-by: Colin Cross <ccross@android.com>
Signed-off-by: franciscofranco <franciscofranco.1990@gmail.com>
Staging: android: binder: Add binder buffers to kmemleak

Some binder_transaction structs are only referenced by a
binder_buffer. This could cause kmemleak to report them as
unreferenced.

Change-Id: I939540faa547afac4284f70f0e08ceb57a7a823d
Signed-off-by: Arve Hjønnevåg <arve@android.com>
Signed-off-by: franciscofranco <franciscofranco.1990@gmail.com>