1. 01 12月, 2008 1 次提交
  2. 21 6月, 2008 1 次提交
    • I
      alpha: fix compile failures with gcc-4.3 (bug #10438) · d559d4a2
      Ivan Kokshaysky 提交于
      Vast majority of these build failures are gcc-4.3 warnings
      about static functions and objects being referenced from
      non-static (read: "extern inline") functions, in conjunction
      with our -Werror.
      
      We cannot just convert "extern inline" to "static inline",
      as people keep suggesting all the time, because "extern inline"
      logic is crucial for generic kernel build.
      So
      - just make sure that all callees of critical "extern inline"
        functions are also "extern inline";
      - use "static inline", wherever it's possible.
      
      traps.c: work around gcc-4.3 being too smart about array
      bounds-checking.
      
      TODO: add "gnu_inline" attribute to all our "extern inline"
      functions to ensure desired behaviour with future compilers.
      Signed-off-by: NIvan Kokshaysky <ink@jurassic.park.msu.ru>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      d559d4a2
  3. 28 4月, 2008 1 次提交
  4. 20 10月, 2007 1 次提交
  5. 18 7月, 2007 1 次提交
  6. 01 7月, 2006 1 次提交
  7. 03 10月, 2005 1 次提交
  8. 01 7月, 2005 1 次提交
    • I
      [PATCH] alpha smp fix · eaf05be0
      Ivan Kokshaysky 提交于
      As usual, the reason of this breakage is quite silly: in do_entIF, we
      are checking for PS == 0 to see whether it was a kernel BUG() or
      userspace trap.
      
      It works, unless BUG() happens in interrupt - PS is not 0 in kernel mode
      due to non-zero IPL, and the things get messed up horribly then.  In
      this particular case it was BUG_ON(!irqs_disabled()) triggered in
      run_posix_cpu_timers(), so we ended up shooting "current" with the
      bursts of one SIGTRAP and three SIGILLs on every timer tick.  ;-)
      eaf05be0
  9. 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