1. 17 12月, 2009 1 次提交
  2. 25 6月, 2009 1 次提交
  3. 28 4月, 2009 1 次提交
    • Y
      irq: change ->set_affinity() to return status · d5dedd45
      Yinghai Lu 提交于
      according to Ingo, change set_affinity() in irq_chip should return int,
      because that way we can handle failure cases in a much cleaner way, in
      the genirq layer.
      
      v2: fix two typos
      
      [ Impact: extend API ]
      Signed-off-by: NYinghai Lu <yinghai@kernel.org>
      Cc: Andrew Morton <akpm@linux-foundation.org>
      Cc: Suresh Siddha <suresh.b.siddha@intel.com>
      Cc: "Eric W. Biederman" <ebiederm@xmission.com>
      Cc: Rusty Russell <rusty@rustcorp.com.au>
      Cc: linux-arch@vger.kernel.org
      LKML-Reference: <49F654E9.4070809@kernel.org>
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      d5dedd45
  4. 13 1月, 2009 1 次提交
  5. 13 12月, 2008 1 次提交
  6. 11 10月, 2008 1 次提交
  7. 12 10月, 2007 1 次提交
  8. 25 9月, 2007 1 次提交
  9. 13 7月, 2007 1 次提交
    • K
      [MIPS] SMTC: Interrupt mask backstop hack · 0db34215
      Kevin D. Kissell 提交于
      To support multiple TC microthreads acting as "CPUs" within a VPE,
      VPE-wide interrupt mask bits must be specially manipulated during
      interrupt handling. To support legacy drivers and interrupt controller
      management code, SMTC has a "backstop" to track and if necessary restore
      the interrupt mask. This has some performance impact on interrupt service
      overhead. Disable it only if you know what you are doing.
      Signed-off-by: NRalf Baechle <ralf@linux-mips.org>
      0db34215
  10. 21 6月, 2007 1 次提交
  11. 07 2月, 2007 1 次提交
  12. 09 1月, 2007 1 次提交
  13. 30 11月, 2006 2 次提交
  14. 07 11月, 2006 1 次提交
  15. 12 10月, 2006 1 次提交
  16. 08 10月, 2006 1 次提交
  17. 27 9月, 2006 1 次提交
  18. 30 6月, 2006 1 次提交
  19. 26 4月, 2006 1 次提交
  20. 19 4月, 2006 2 次提交
  21. 30 10月, 2005 1 次提交
  22. 10 9月, 2005 1 次提交
  23. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4