Linux 3.4.1 -> 3.4.74

Conflicts:
	arch/arm/kernel/perf_event.c
	arch/arm/mm/dma-mapping.c
	drivers/base/power/main.c
	drivers/gpu/drm/radeon/radeon_mode.h
	drivers/mmc/host/sdhci.c
	drivers/usb/core/hub.c
	fs/buffer.c
	fs/ecryptfs/mmap.c
	fs/jbd2/transaction.c
	include/net/tcp.h
	kernel/hrtimer.c
	mm/vmscan.c
	net/ipv4/fib_semantics.c
	net/irda/af_irda.c

Conflicts:
	arch/arm/kernel/perf_event.c
	drivers/base/power/main.c
	drivers/gpu/drm/radeon/radeon_mode.h
	drivers/mmc/host/sdhci.c
	fs/buffer.c
	include/net/tcp.h
	include/trace/events/random.h
	mm/vmscan.c
	net/irda/af_irda.c
	net/wireless/reg.c
Linux 3.4.75 -> 3.4.95

Conflicts:
	fs/ecryptfs/keystore.c
	mm/vmscan.c

Conflicts:
	drivers/char/random.c
	mm/vmscan.c
Turn off -Wmaybe-uninitialized when building with -Os

gcc-4.7 and higher add a lot of false positive warnings about
potential uses of uninitialized warnings, but only when optimizing
for size (-Os). This is the default when building allyesconfig,
which turns on CONFIG_CC_OPTIMIZE_FOR_SIZE.

In order to avoid getting a lot of patches that initialize such
variables and accidentally hide real errors along the way, let's
just turn off this warning on the respective gcc versions
when building with size optimizations. The -Wmaybe-uninitialized
option was introduced in the same gcc version (4.7) that is now
causing the false positives, so there is no effect on older compilers.

A side effect is that when building with CONFIG_CC_OPTIMIZE_FOR_SIZE,
we might now see /fewer/ warnings about possibly uninitialized
warnings than with -O2, but that is still much better than seeing
warnings known to be bogus.

Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Git-commit: e74fc973b6e531fef1fce8b101ffff05ecfb774c
Git-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
Signed-off-by: Bryan Huntsman <bryanh@codeaurora.org>