compiler/gcc4: Add quirk for 'asm goto' miscompilation bug

commit 3f0116c3238a96bc18ad4b4acefe4e7be32fa861 upstream.

Fengguang Wu, Oleg Nesterov and Peter Zijlstra tracked down
a kernel crash to a GCC bug: GCC miscompiles certain 'asm goto'
constructs, as outlined here:

  http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58670

Implement a workaround suggested by Jakub Jelinek.

Reported-and-tested-by: Fengguang Wu <fengguang.wu@intel.com>
Reported-by: Oleg Nesterov <oleg@redhat.com>
Reported-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Suggested-by: Jakub Jelinek <jakub@redhat.com>
Reviewed-by: Richard Henderson <rth@twiddle.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
[hq: Backported to 3.4: Adjust context]
Signed-off-by: Qiang Huang <h.huangqiang@huawei.com>
Cc: Li Zefan <lizefan@huawei.com>
Cc: Jianguo Wu <wujianguo@huawei.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
fixing 'make headers_check' error messages

Signed-off-by: moddingg33k <moddingg33k@t-online.de>
ARM: 7674/1: smp: Avoid dummy clockevent being preferred over real hardware clock-event

With recent arm broadcast time clean-up from Mark Rutland, the dummy
broadcast device is always registered with timer subsystem. And since
the rating of the dummy clock event is very high, it may be preferred
over a real clock event.

This is a change in behavior from past and not an intended one. So
reduce the rating of the dummy clock-event so that real clock-event
device is selected when available.

Acked-by: Thomas Gleixner <tglx@linutronix.de>
Acked-by: Mark Rutland <mark.rutland@arm.com>
Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
ARM: Allow arm_memblock_steal() to remove memory from any RAM region

Allow arm_memblock_steal() to remove memory from any RAM region,
including highmem areas.  This allows memory to be stolen from the
very top of declared memory, including highmem areas, rather than
our precious lowmem.

Acked-by: Sascha Hauer <s.hauer@pengutronix.de>
Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
ARM: swp_emulate: *squashing updates*

ARM: missing ->mmap_sem around find_vma() in swp_emulate.c

	find_vma() is *not* safe when somebody else is removing vmas.  Not just
	the return value might get bogus just as you are getting it (this instance
	doesn't try to dereference the resulting vma), the search itself can get
	buggered in rather spectacular ways.  IOW, ->mmap_sem really, really is
	not optional here.

	Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
	Cc: <stable@vger.kernel.org>
	Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>

get rid of a bunch of open-coded create_proc_read_entry()

arm: Don't use create_proc_read_entry()

	Don't use create_proc_read_entry() as that is deprecated, but rather use
	proc_create_data() and seq_file instead.

	Signed-off-by: David Howells <dhowells@redhat.com>
	Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
arm: common: fix cpaccess asm instruction

The write_val argument was not specified as an input
on the asm instruction. The compiler thought it wasn't used,
even though the asm instruction does use r0, which
is how write_val is passed into the function. The compiler
would optimise out the argument being passed into
the function.

Add write_val as an input operand to prevent it being
optimised out.

Change-Id: I71f35e1b2e3c655f4020163d089d9c71bbd6614b
Signed-off-by: Neil Leeder <nleeder@codeaurora.org>
drivers/cpufreq: conservative: simplify SAMPLING_TIME determination for ARM

...because simple things can be good things, too.

This commit introduces MIN_SAMPLING_RATE & DEF_SAMPLING_RATE
which are used to directly set the driver's minimum and default
sampling rate rather than doing any calculation before.

Signed-off-by: moddingg33k <moddingg33k@t-online.de>
huawei_battery.c: reduced charging voltage from 4350 mV to 4300 mV

...to prevent overcharging and increasing battery's longevity.

Signed-off-by: moddingg33k <moddingg33k@t-online.de>
huawei_battery.c: decrease BATTERY_HIGH_HIGH & HEALTH_HIGH_VOLT_MAX to 4350

Signed-off-by: moddingg33k <moddingg33k@t-online.de>
huawei_battery.c: increase RPC polling from 5sec to 60sec

Signed-off-by: moddingg33k <moddingg33k@t-online.de>
Version 0.50