1. 16 Nov, 2016 1 commit
  2. 28 Oct, 2016 34 commits
  3. 27 Oct, 2016 5 commits
    • Linus Torvalds's avatar
      Allow KASAN and HOTPLUG_MEMORY to co-exist when doing build testing · 67463e54
      Linus Torvalds authored
      No, KASAN may not be able to co-exist with HOTPLUG_MEMORY at runtime,
      but for build testing there is no reason not to allow them together.
      
      This hopefully means better build coverage and fewer embarrasing silly
      problems like the one fixed by commit 9db4f36e ("mm: remove unused
      variable in memory hotplug") in the future.
      
      Cc: Stephen Rothwell <sfr@canb.auug.org.au>
      Cc: Andrey Ryabinin <aryabinin@virtuozzo.com>
      Cc: Alexander Potapenko <glider@google.com>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      67463e54
    • Arnd Bergmann's avatar
      nvdimm: make CONFIG_NVDIMM_DAX 'bool' · 867dfe34
      Arnd Bergmann authored
      A bugfix just tried to address a randconfig build problem and introduced
      a variant of the same problem: with CONFIG_LIBNVDIMM=y and
      CONFIG_NVDIMM_DAX=m, the nvdimm module now fails to link:
      
      drivers/nvdimm/built-in.o: In function `to_nd_device_type':
      bus.c:(.text+0x1b5d): undefined reference to `is_nd_dax'
      drivers/nvdimm/built-in.o: In function `nd_region_notify_driver_action.constprop.2':
      region_devs.c:(.text+0x6b6c): undefined reference to `is_nd_dax'
      region_devs.c:(.text+0x6b8c): undefined reference to `to_nd_dax'
      drivers/nvdimm/built-in.o: In function `nd_region_probe':
      region.c:(.text+0x70f3): undefined reference to `nd_dax_create'
      drivers/nvdimm/built-in.o: In function `mode_show':
      namespace_devs.c:(.text+0xa196): undefined reference to `is_nd_dax'
      drivers/nvdimm/built-in.o: In function `nvdimm_namespace_common_probe':
      (.text+0xa55f): undefined reference to `is_nd_dax'
      drivers/nvdimm/built-in.o: In function `nvdimm_namespace_common_probe':
      (.text+0xa56e): undefined reference to `to_nd_dax'
      
      This reverts the earlier fix, making NVDIMM_DAX a 'bool' option again
      as it should be (it gets linked into the libnvdimm module). To fix
      the original problem, I'm adding a dependency on LIBNVDIMM to
      DEV_DAX_PMEM, which ensures we can't have that one built-in if the
      rest is a module.
      
      Fixes: 4e65e938 ("/dev/dax: fix Kconfig dependency build breakage")
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      Reviewed-by: default avatarRoss Zwisler <ross.zwisler@linux.intel.com>
      Signed-off-by: default avatarDan Williams <dan.j.williams@intel.com>
      867dfe34
    • Linus Torvalds's avatar
      mm: remove unused variable in memory hotplug · 9db4f36e
      Linus Torvalds authored
      When I removed the per-zone bitlock hashed waitqueues in commit
      9dcb8b68 ("mm: remove per-zone hashtable of bitlock waitqueues"), I
      removed all the magic hotplug memory initialization of said waitqueues
      too.
      
      But when I actually _tested_ the resulting build, I stupidly assumed
      that "allmodconfig" would enable memory hotplug.  And it doesn't,
      because it enables KASAN instead, which then disables hotplug memory
      support.
      
      As a result, my build test of the per-zone waitqueues was totally
      broken, and I didn't notice that the compiler warns about the now unused
      iterator variable 'i'.
      
      I guess I should be happy that that seems to be the worst breakage from
      my clearly horribly failed test coverage.
      Reported-by: default avatarStephen Rothwell <sfr@canb.auug.org.au>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      9db4f36e
    • Linus Torvalds's avatar
      Merge branch 'i2c/for-current' of git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux · 4e68af0b
      Linus Torvalds authored
      Pull i2c fixes from Wolfram Sang:
       "I2C has some driver bugfixes, module autoload fixes, and driver
        enablement on some architectures"
      
      * 'i2c/for-current' of git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux:
        i2c: imx: defer probe if bus recovery GPIOs are not ready
        i2c: designware: Avoid aborted transfers with fast reacting I2C slaves
        i2c: i801: Fix I2C Block Read on 8-Series/C220 and later
        i2c: xgene: Avoid dma_buffer overrun
        i2c: digicolor: Fix module autoload
        i2c: xlr: Fix module autoload for OF registration
        i2c: xlp9xx: Fix module autoload
        i2c: jz4780: Fix module autoload
        i2c: allow configuration of imx driver for ColdFire architecture
        i2c: mark device nodes only in case of successful instantiation
        i2c: rk3x: Give the tuning value 0 during rk3x_i2c_v0_calc_timings
        i2c: hix5hd2: allow build with ARCH_HISI
      4e68af0b
    • Linus Torvalds's avatar
      Merge branch 'next' of git://git.kernel.org/pub/scm/linux/kernel/git/rzhang/linux · 7f2145b0
      Linus Torvalds authored
      Pull thermal updates from Zhang Rui:
       "The latest Thermal Management updates for v4.9-rc3:
      
         - Fix a regression introduced by commit
           b721ca0d(thermal/powerclamp: remove cpu whitelist), that
           powerclamp driver checks cpu support in a wrong way. From: Eric
           Ernst.
      
         - Fix a problem that intel_pch_thermal driver misses passive trip
           point when the PCH thermal device has an ACPI companion device
           associated. From: Srinivas Pandruvada.
      
         - Add missing support for Haswell PCH thermal sensor. From: Srinivas
           Pandruvada"
      
      * 'next' of git://git.kernel.org/pub/scm/linux/kernel/git/rzhang/linux:
        thermal/powerclamp: correct cpu support check
        thermal: intel_pch_thermal: Enable Haswell PCH
        thermal: intel_pch_thermal: Add an ACPI passive trip
      7f2145b0