Squashed: Fix battery drain

After applying the cpufreq cpu-boost driver commits,
all cpu cores are always online when i checked them.

This causes a really high battery drain.
As it harms more than it brings performance, lets
revert it.

------------------------------------------------------

Revert "cpufreq: Add a sync limit to cpu-boost"

This reverts commit 35e64d6089f5ef5a808089596fb09a52a05be85c.

-------------------------------------------------------

Revert "cpufreq: Add cpu-boost driver"

This reverts commit 508832817d7af22f2c5415bac1853d9790d91a15.

-------------------------------------------------------

Change-Id: If14e21ccc64c390c2622b276a3b879c743b3c576
bcmdhd: update to 1.88.51 from gpe 4.4

Change-Id: Ide40296c73e000798e174c9043a4cb8ec6a82639
Revert "Squashed: Fix battery drain"

The problem lies somewhere else

This reverts commit 01e989d451fc20f2ea4affe3b493bb8aa78ad930.

Change-Id: I1aa95b167d0d1997219d291dad17350d12462ef4
ext4: fix memory leak in xattr

If we take the 2nd retry path in ext4_expand_extra_isize_ea, we
potentionally return from the function without having freed these
allocations.  If we don't do the return, we over-write the previous
allocation pointers, so we leak either way.

Spotted with Coverity.

[ Fixed by tytso to set is and bs to NULL after freeing these
  pointers, in case in the retry loop we later end up triggering an
  error causing a jump to cleanup, at which point we could have a double
  free bug. -- Ted ]

Signed-off-by: Dave Jones <davej@fedoraproject.org>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Reviewed-by: Eric Sandeen <sandeen@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Change-Id: I825a85c81d66ef115857980630097edf32296af2
Merge branch 'my-omni-4.4', remote-tracking branch 'omni-kernel-upstream/android-4.4' into my-omni-4.4
A little change!