1. 16 12月, 2009 2 次提交
  2. 14 12月, 2009 5 次提交
  3. 02 12月, 2009 1 次提交
  4. 12 11月, 2009 1 次提交
  5. 29 10月, 2009 1 次提交
    • M
      twl4030-gpio: remove __devexit markings from remove func · 46c529cf
      Mike Frysinger 提交于
      The gpio_twl4030_probe() function calls gpio_twl4030_remove(), and the
      former has __devinit, so the latter cannot use __devexit.  Otherwise we
      hit the section mismatch warning:
      
      WARNING: drivers/gpio/built-in.o(.devinit.text+0x71a): Section mismatch
      	in reference from the function _gpio_twl4030_probe() to the function
      	.devexit.text:_gpio_twl4030_remove()
      The function __devinit _gpio_twl4030_probe() references a function
      	__devexit _gpio_twl4030_remove().
      This is often seen when error handling in the init function uses
      	functionality in the exit path.
      The fix is often to remove the __devexit annotation of
      	_gpio_twl4030_remove() so it may be used outside an exit section.
      Signed-off-by: NMike Frysinger <vapier@gentoo.org>
      Cc: David Brownell <david-b@pacbell.net>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      46c529cf
  6. 02 10月, 2009 1 次提交
  7. 23 9月, 2009 9 次提交
  8. 21 9月, 2009 1 次提交
  9. 19 9月, 2009 1 次提交
  10. 17 9月, 2009 1 次提交
  11. 13 7月, 2009 1 次提交
  12. 03 7月, 2009 2 次提交
  13. 01 7月, 2009 2 次提交
  14. 20 6月, 2009 1 次提交
  15. 19 6月, 2009 4 次提交
  16. 21 5月, 2009 1 次提交
  17. 03 4月, 2009 2 次提交
  18. 30 3月, 2009 1 次提交
  19. 25 3月, 2009 1 次提交
  20. 30 1月, 2009 1 次提交
  21. 16 1月, 2009 1 次提交
    • B
      gpio: fix probe() error return in gpio driver probes · a342d215
      Ben Dooks 提交于
      A number of drivers in drivers/gpio return -ENODEV when confronted with
      missing setup parameters such as the platform data.  However, returning
      -ENODEV causes the driver layer to silently ignore the driver as it
      assumes the probe did not find anything and was only speculative.
      
      To make life easier to discern why a driver is not being attached, change
      to returning -EINVAL, which is a better description of the fact that the
      driver data was not valid.
      
      Also add a set of dev_dbg() statements to the error paths to provide an
      better explanation of the error as there may be more that one point in the
      driver.
      Signed-off-by: NBen Dooks <ben-linux@fluff.org>
      Cc: David Brownell <david-b@pacbell.net>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      a342d215