1. 08 1月, 2010 1 次提交
  2. 04 12月, 2009 1 次提交
  3. 17 11月, 2009 1 次提交
  4. 16 11月, 2009 1 次提交
  5. 13 11月, 2009 1 次提交
  6. 09 11月, 2009 1 次提交
  7. 07 11月, 2009 1 次提交
  8. 05 11月, 2009 1 次提交
  9. 30 10月, 2009 2 次提交
  10. 21 9月, 2009 2 次提交
  11. 26 8月, 2009 1 次提交
  12. 10 8月, 2009 1 次提交
  13. 29 7月, 2009 2 次提交
  14. 30 6月, 2009 1 次提交
  15. 25 6月, 2009 1 次提交
  16. 17 6月, 2009 1 次提交
    • A
      time: move PIT_TICK_RATE to linux/timex.h · 08604bd9
      Arnd Bergmann 提交于
      PIT_TICK_RATE is currently defined in four architectures, but in three
      different places.  While linux/timex.h is not the perfect place for it, it
      is still a reasonable replacement for those drivers that traditionally use
      asm/timex.h to get CLOCK_TICK_RATE and expect it to be the PIT frequency.
      
      Note that for Alpha, the actual value changed from 1193182UL to 1193180UL.
       This is unlikely to make a difference, and probably can only improve
      accuracy.  There was a discussion on the correct value of CLOCK_TICK_RATE
      a few years ago, after which every existing instance was getting changed
      to 1193182.  According to the specification, it should be
      1193181.818181...
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Cc: Richard Henderson <rth@twiddle.net>
      Cc: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
      Cc: Ralf Baechle <ralf@linux-mips.org>
      Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
      Cc: Ingo Molnar <mingo@elte.hu>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Cc: "H. Peter Anvin" <hpa@zytor.com>
      Cc: Len Brown <lenb@kernel.org>
      Cc: john stultz <johnstul@us.ibm.com>
      Cc: Dmitry Torokhov <dtor@mail.ru>
      Cc: Takashi Iwai <tiwai@suse.de>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      08604bd9
  17. 13 6月, 2009 1 次提交
  18. 15 5月, 2009 1 次提交
  19. 13 5月, 2009 1 次提交
  20. 30 3月, 2009 1 次提交
  21. 27 3月, 2009 1 次提交
  22. 16 3月, 2009 1 次提交
    • J
      Use f_lock to protect f_flags · db1dd4d3
      Jonathan Corbet 提交于
      Traditionally, changes to struct file->f_flags have been done under BKL
      protection, or with no protection at all.  This patch causes all f_flags
      changes after file open/creation time to be done under protection of
      f_lock.  This allows the removal of some BKL usage and fixes a number of
      longstanding (if microscopic) races.
      Reviewed-by: NChristoph Hellwig <hch@lst.de>
      Cc: Al Viro <viro@ZenIV.linux.org.uk>
      Signed-off-by: NJonathan Corbet <corbet@lwn.net>
      db1dd4d3
  23. 26 2月, 2009 2 次提交
  24. 23 2月, 2009 1 次提交
  25. 18 2月, 2009 1 次提交
  26. 17 2月, 2009 1 次提交
  27. 16 2月, 2009 1 次提交
  28. 11 2月, 2009 1 次提交
  29. 13 1月, 2009 1 次提交
  30. 06 1月, 2009 1 次提交
  31. 13 12月, 2008 1 次提交
  32. 02 11月, 2008 1 次提交
  33. 27 10月, 2008 1 次提交
  34. 21 10月, 2008 1 次提交
  35. 20 10月, 2008 1 次提交
  36. 17 10月, 2008 1 次提交