msm8974: Add UIO region for NV recovery system

Change-Id: I55823b9137cb658bcff1dffb083f7107695b1c97
asoc: msm: Fix compress capture

 * Capture endpoints were not being properly registered, resulting in
   failure to record AMR_WB formats. Fix it.

Change-Id: I898cfdabce862ab4f551c2903e53fe1d3d76a368
defconfig: add own for Aurora Kernel
fs: fix warnings due to uninitialized vars
Makefile: no warnings for sizeof-pointer-memaccess in Bluetooth
ramfs: add current cm ramfs
Merge remote-tracking branch 'upstream/cm-11.0' into cm11-aosp-nightly
LZ4: add support for LZ4 compression
lz4: Restore version that compiles properly

Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>
lz4: Sync up with latest version

Thanks @labodj for heads up.

Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>
LZ4: fix last LZ4_COMPRESSBOUND to lower case.
lz4: ensure length does not wrap

Given some pathologically compressed data, lz4 could possibly decide to
wrap a few internal variables, causing unknown things to happen.  Catch
this before the wrapping happens and abort the decompression.

Reported-by: "Don A. Bailey" <donb@securitymouse.com>
Cc: stable <stable@vger.kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
lz4: fix another possible overrun

There is one other possible overrun in the lz4 code as implemented by
Linux at this point in time (which differs from the upstream lz4
codebase, but will get synced at in a future kernel release.)  As
pointed out by Don, we also need to check the overflow in the data
itself.

While we are at it, replace the odd error return value with just a
"simple" -1 value as the return value is never used for anything other
than a basic "did this work or not" check.

Reported-by: "Don A. Bailey" <donb@securitymouse.com>
Reported-by: Willy Tarreau <w@1wt.eu>
Cc: stable <stable@vger.kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
lz4: add overrun checks to lz4_uncompress_unknownoutputsize()

Jan points out that I forgot to make the needed fixes to the
lz4_uncompress_unknownoutputsize() function to mirror the changes done
in lz4_decompress() with regards to potential pointer overflows.

The only in-kernel user of this function is the zram code, which only
takes data from a valid compressed buffer that it made itself, so it's
not a big issue.  But due to external kernel modules using this
function, it's better to be safe here.

Reported-by: Jan Beulich <JBeulich@suse.com>
Cc: "Don A. Bailey" <donb@securitymouse.com>
Cc: stable <stable@vger.kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
add build scripts
cpufreq: add latest intelliactive gov
power: add powersuspend