lib/sha1: use the git implementation of SHA-1

For ChromiumOS, we use SHA-1 to verify the integrity of the root
filesystem.  The speed of the kernel sha-1 implementation has a major
impact on our boot performance.

To improve boot performance, we investigated using the heavily optimized
sha-1 implementation used in git.  With the git sha-1 implementation, we
see a 11.7% improvement in boot time.

10 reboots, remove slowest/fastest.

Before:

  Mean: 6.58 seconds Stdev: 0.14

After (with git sha-1, this patch):

  Mean: 5.89 seconds Stdev: 0.07

The other cool thing about the git SHA-1 implementation is that it only
needs 64 bytes of stack for the workspace while the original kernel
implementation needed 320 bytes.

Signed-off-by: Mandeep Singh Baines <msb@chromium.org>
Cc: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
Cc: Nicolas Pitre <nico@cam.org>
Cc: Herbert Xu <herbert@gondor.apana.org.au>
Cc: David S. Miller <davem@davemloft.net>
Cc: linux-crypto@vger.kernel.org
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
arm: remove "optimized" SHA1 routines

Since commit 1eb19a12bd22 ("lib/sha1: use the git implementation of
SHA-1"), the ARM SHA1 routines no longer work.  The reason? They
depended on the larger 320-byte workspace, and now the sha1 workspace is
just 16 words (64 bytes).  So the assembly version would overwrite the
stack randomly.

The optimized asm version is also probably slower than the new improved
C version, so there's no reason to keep it around.  At least that was
the case in git, where what appears to be the same assembly language
version was removed two years ago because the optimized C BLK_SHA1 code
was faster.

Reported-and-tested-by: Joachim Eastwood <manabian@gmail.com>
Cc: Andreas Schwab <schwab@linux-m68k.org>
Cc: Nicolas Pitre <nico@fluxnic.net>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
sched: Don't call task_group() too many times in set_task_rq()

It improves perfomance, especially if autogroup is enabled.

The size of set_task_rq() was 0x180 and now it is 0xa0.

Signed-off-by: Andrew Vagin <avagin@openvz.org>
Acked-by: Paul Turner <pjt@google.com>
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Link: http://lkml.kernel.org/r/1321020240-3874331-1-git-send-email-avagin@openvz.org
Signed-off-by: Ingo Molnar <mingo@elte.hu>
lib/sha1.c: quiet sparse noise about symbol not declared

Include <linux/cryptohash.h> to pickup the declarations for sha_transform
and sha_init to quite the sparse noise:

  warning: symbol 'sha_transform' was not declared. Should it be static?
  warning: symbol 'sha_init' was not declared. Should it be static?

Signed-off-by: H Hartley Sweeten <hsweeten@visionengravers.com>
Acked-by: Mandeep Singh Baines <msb@chromium.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
arm: remove stale export of 'sha_transform'

The generic library code already exports the generic function, this was
left-over from the ARM-specific version that just got removed.

Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
modem_if: Stop printing [MIF] messages
sec_battery: Make driver less chatty.

Change-Id: I88a47c5287b690f1b2645ed2ac1dfcbefb65adab
max17042: Make driver less chatty

Make a bunch of the debug stuff depend on CONFIG_POWER_SUPPLY_DEBUG

Change-Id: Ia47b6eba281dad6bf9a44908d1e13814c7872720
mach-u1: Make SoC "need recal" check shut up

There's no reason for this to print something out EVERY DAMN TIME.

Change-Id: Ie3e1d59979c74d2019f180818e85bf3bb77cc356
config: Increase log buffer size.

128k is a bit too small even after giving the chatty drivers
a dose of STFU.

Change-Id: I9c82c81f4079cc3b10a627cf9d76f9c3fbbc3f43
net: wireless: bcmdhd: Driver update from N7000 Update 3 sources
config: Set country/region code
bcmdhd: enable pno support, change initial scan, fixes wifi direct

Change-Id: I20728809ca236b65c573c2db186f24908e340661
mmc: Pull in N7000 Update3 mmc drivers, disable MMC_CAP_ERASE

Disabling MMC_CAP_ERASE prevents sending ERASE commands from
being sent to the eMMC chip in all circumstances, protecting
it from choking on a command it can't handle because
Samsung failed epically at testing JEDEC eMMC compliance.
(It's obvious they didn't test ERASE at all on MAG4FA, VYL00M,
and KYL00M fwrev 0x19)

Since nearly all devices this kernel runs on have VYL00M, KYL00M,
or MAG4FA fwrev 0x19, MMC_CAP_ERASE *must* be disabled for MSHCI.
Samsung were idiots for enabling it on a device that they STILL
ship with defective eMMC chips.

The MMC drivers contain all sorts of fixes that seem connected to
SDIO power management, so hopefully will fix the recent wifi
resume issues since merging the N7000 Update3 bcmdhd driver.

Also bring in gokhanmoral's fix to bring back TriangleAway support.

Change-Id: Iaedcce029ad23d3fa80081747485157900657f0b
Signed-off-by: Andrew Dodd <atd7@cornell.edu>
mmc: Fix file permissions from N7000 commit
keyboard: cypress: Ensure light is off, enable regulator only if needed
Linux 3.0.35

Changelog:
http://www.kernel.org/pub/linux/kernel/v3.0/ChangeLog-3.0.35
Merge remote-tracking branch 'upstream/master'