1. 20 8月, 2009 1 次提交
  2. 05 8月, 2009 1 次提交
  3. 02 8月, 2009 1 次提交
  4. 27 7月, 2009 2 次提交
  5. 08 7月, 2009 2 次提交
  6. 29 6月, 2009 1 次提交
  7. 11 6月, 2009 1 次提交
    • L
      [ARM] 5544/1: Trust PrimeCell resource sizes · dc890c2d
      Linus Walleij 提交于
      I found the PrimeCell/AMBA Bus drivers distrusting the resource
      passed in as part of the struct amba_device abstraction. This
      patch removes all hard coded resource sizes found in the PrimeCell
      drivers and move the responsibility of this definition back to
      the platform/board device definition, which already exist and
      appear to be correct for all in-tree users of these drivers.
      We do this using the resource_size() inline function which was
      also replicated in the only driver using the resource size, so
      that has been changed too. The KMI_SIZE was left in kmi.h in case
      someone likes it. Test-compiled against Versatile and Integrator
      defconfigs, seems to work but I don't posess these boards and
      cannot test them.
      Signed-off-by: NLinus Walleij <linus.walleij@stericsson.com>
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      dc890c2d
  8. 29 5月, 2009 1 次提交
  9. 21 5月, 2009 2 次提交
  10. 10 5月, 2009 1 次提交
  11. 22 4月, 2009 1 次提交
  12. 18 4月, 2009 2 次提交
  13. 12 4月, 2009 2 次提交
  14. 08 4月, 2009 1 次提交
  15. 25 3月, 2009 1 次提交
  16. 16 3月, 2009 1 次提交
    • J
      Rationalize fasync return values · 60aa4924
      Jonathan Corbet 提交于
      Most fasync implementations do something like:
      
           return fasync_helper(...);
      
      But fasync_helper() will return a positive value at times - a feature used
      in at least one place.  Thus, a number of other drivers do:
      
           err = fasync_helper(...);
           if (err < 0)
                   return err;
           return 0;
      
      In the interests of consistency and more concise code, it makes sense to
      map positive return values onto zero where ->fasync() is called.
      
      Cc: Al Viro <viro@ZenIV.linux.org.uk>
      Signed-off-by: NJonathan Corbet <corbet@lwn.net>
      60aa4924
  17. 02 2月, 2009 1 次提交
  18. 30 1月, 2009 1 次提交
  19. 06 1月, 2009 1 次提交
  20. 30 12月, 2008 1 次提交
  21. 20 12月, 2008 1 次提交
  22. 27 11月, 2008 1 次提交
  23. 25 11月, 2008 1 次提交
  24. 20 11月, 2008 1 次提交
  25. 12 11月, 2008 1 次提交
  26. 02 11月, 2008 1 次提交
    • A
      saner FASYNC handling on file close · 233e70f4
      Al Viro 提交于
      As it is, all instances of ->release() for files that have ->fasync()
      need to remember to evict file from fasync lists; forgetting that
      creates a hole and we actually have a bunch that *does* forget.
      
      So let's keep our lives simple - let __fput() check FASYNC in
      file->f_flags and call ->fasync() there if it's been set.  And lose that
      crap in ->release() instances - leaving it there is still valid, but we
      don't have to bother anymore.
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      233e70f4
  27. 30 10月, 2008 1 次提交
  28. 28 10月, 2008 1 次提交
  29. 17 10月, 2008 1 次提交
  30. 15 10月, 2008 1 次提交
  31. 14 10月, 2008 1 次提交
  32. 23 9月, 2008 1 次提交
  33. 11 9月, 2008 1 次提交
  34. 05 9月, 2008 1 次提交
  35. 31 8月, 2008 1 次提交