Merge branch 'linus' into x86/cleanups, before applying dependent patch

The addresses are normal I2C addresses.  The adapter is the string

name of the adapter, as shown in /sys/class/i2c-adapter/i2c-<n>/name.

It is *NOT* i2c-<n> itself.

It is *NOT* i2c-<n> itself.  Also, the comparison is done ignoring

spaces, so if the name is "This is an I2C chip" you can say

adapter_name=ThisisanI2cchip.  This is because it's hard to pass in

spaces in kernel parameters.

The debug flags are bit flags for each BMC found, they are:

IPMI messages: 1, driver state: 2, timing: 4, I2C probe: 8

GPIO support

~~~~~~~~~~~~

ACPI 5 introduced two new resources to describe GPIO connections: GpioIo

and GpioInt. These resources are used be used to pass GPIO numbers used by

and GpioInt. These resources can be used to pass GPIO numbers used by

the device to the driver. ACPI 5.1 extended this with _DSD (Device

Specific Data) which made it possible to name the GPIOs among other things.

_DSD Device Properties Related to GPIO

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

With the release of ACPI 5.1 and the _DSD configuration objecte names

can finally be given to GPIOs (and other things as well) returned by

_CRS.  Previously, we were only able to use an integer index to find

With the release of ACPI 5.1, the _DSD configuration object finally

allows names to be given to GPIOs (and other things as well) returned

by _CRS.  Previously, we were only able to use an integer index to find

the corresponding GPIO, which is pretty error prone (it depends on

the _CRS output ordering, for example).

Abracon ABX80X I2C ultra low power RTC/Alarm chip

The Abracon ABX80X family consist of the ab0801, ab0803, ab0804, ab0805, ab1801,

ab1803, ab1804 and ab1805. The ab0805 is the superset of ab080x and the ab1805

is the superset of ab180x.

Required properties:

 - "compatible": should one of:

        "abracon,abx80x"

        "abracon,ab0801"

        "abracon,ab0803"

        "abracon,ab0804"

        "abracon,ab0805"

        "abracon,ab1801"

        "abracon,ab1803"

        "abracon,ab1804"

        "abracon,ab1805"

	Using "abracon,abx80x" will enable chip autodetection.

 - "reg": I2C bus address of the device

Optional properties:

The abx804 and abx805 have a trickle charger that is able to charge the

connected battery or supercap. Both the following properties have to be defined

and valid to enable charging:

 - "abracon,tc-diode": should be "standard" (0.6V) or "schottky" (0.3V)

 - "abracon,tc-resistor": should be <0>, <3>, <6> or <11>. 0 disables the output

                          resistor, the other values are in ohm.

bugs.

KASan uses compile-time instrumentation for checking every memory access,

therefore you will need a certain version of GCC > 4.9.2

therefore you will need a gcc version of 4.9.2 or later. KASan could detect out

of bounds accesses to stack or global variables, but only if gcc 5.0 or later was

used to built the kernel.

Currently KASan is supported only for x86_64 architecture and requires that the

kernel be built with the SLUB allocator.

and choose between CONFIG_KASAN_OUTLINE and CONFIG_KASAN_INLINE. Outline/inline

is compiler instrumentation types. The former produces smaller binary the

latter is 1.1 - 2 times faster. Inline instrumentation requires GCC 5.0 or

latter.

latter is 1.1 - 2 times faster. Inline instrumentation requires a gcc version

of 5.0 or later.

Currently KASAN works only with the SLUB memory allocator.

For better bug detection and nicer report, enable CONFIG_STACKTRACE and put