1. 18 9月, 2012 3 次提交
  2. 17 9月, 2012 8 次提交
  3. 16 9月, 2012 3 次提交
  4. 14 9月, 2012 11 次提交
  5. 11 9月, 2012 11 次提交
  6. 24 8月, 2012 1 次提交
    • F
      mfd: lpc_ich: Fix a 3.5 kernel regression for iTCO_wdt driver · 092369ef
      Feng Tang 提交于
      There are many reports (including 2 of my machines) that iTCO_wdt watchdog
      driver fails to be initialized in 3.5 kernel with error message like:
      
      [    5.265175] ACPI Warning: 0x00001060-0x0000107f SystemIO conflicts with Region \_SB_.PCI0.LPCB.TCOI 1 (20120320/utaddress-251)
      [    5.265192] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
      [    5.265206] lpc_ich: Resource conflict(s) found affecting iTCO_wdt
      
      The root cause the iTCO_wdt driver in 3.4 probes the HW IO resource from
      LPC's PCI config space, while in 3.5 kernel it relies on lpc_ich driver
      for the probe, which adds a new acpi_check_resource_conflict() check, and
      give up the probe if there is any conflict with ACPI.
      
      Fix it by removing all the checks for iTCO_wdt to keep the same behavior as
      3.4 kernel.
      https://bugzilla.kernel.org/show_bug.cgi?id=44991
      
      Actually the same check could be removed for the gpio-ich in lpc_ich.c,
      but I'm not sure if it will cause problems.
      Signed-off-by: NFeng Tang <feng.tang@intel.com>
      Cc: Aaron Sierra <asierra@xes-inc.com>
      Cc: Wim Van Sebroeck <wim@iguana.be>
      Cc: Len Brown <len.brown@intel.com>
      Cc: Bob Moore <robert.moore@intel.com>
      Signed-off-by: NSamuel Ortiz <sameo@linux.intel.com>
      092369ef
  7. 22 8月, 2012 1 次提交
    • A
      mfd: Move tps65217 regulator plat data handling to regulator · 817bb7fb
      AnilKumar Ch 提交于
      Regulator platform data handling was mistakenly added to MFD
      driver. So we will see build errors if we compile MFD drivers
      without CONFIG_REGULATOR. This patch moves regulator platform
      data handling from TPS65217 MFD driver to regulator driver.
      
      This makes MFD driver independent of REGULATOR framework so
      build error is fixed if CONFIG_REGULATOR is not set.
      
      drivers/built-in.o: In function `tps65217_probe':
      tps65217.c:(.devinit.text+0x13e37): undefined reference
      to `of_regulator_match'
      
      This patch also fix allocation size of tps65217 platform data.
      Current implementation allocates a struct tps65217_board for each
      regulator specified in the device tree. But the structure itself
      provides array of regulators so one instance of it is sufficient.
      Signed-off-by: NAnilKumar Ch <anilkumar@ti.com>
      817bb7fb
  8. 17 8月, 2012 2 次提交
    • L
      Linux 3.6-rc2 · d9875690
      Linus Torvalds 提交于
      d9875690
    • I
      autofs4 - fix get_next_positive_subdir() · a45440f0
      Ian Kent 提交于
      Following a report of a crash during an automount expire I found that
      the locking in fs/autofs4/expire.c:get_next_positive_subdir() was wrong.
      Not only is the locking wrong but the function is more complex than it
      needs to be.
      
      The function is meant to calculate (and dget) the next entry in the list
      of directories contained in the root of an autofs mount point (an autofs
      indirect mount to be precise). The main problem was that the d_lock of
      the owner of the list was not being taken when walking the list, which
      lead to list corruption under load. The only other lock that needs to
      be taken is against the next dentry candidate so it can be checked for
      usability.
      Signed-off-by: NIan Kent <raven@themaw.net>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      a45440f0