1. 08 2月, 2011 1 次提交
    • G
      m68knommu: fix use of un-defined _TIF_WORK_MASK · b3e338de
      Greg Ungerer 提交于
      The _TIF_WORK_MASK definition was removed in the clean up of MMU and
      non-MMU arch/m68k/include/asm/thread_info*.h files (this was commit
      cddafa35, "merge MMU and non-MMU
      thread_info.h").
      
      It didn't get cleaned out of the entry.S code for the 68328 and 68360
      based platforms. And it was replaced by a hard coded constant mask for
      coldfire platforms. There is currently no need to mask any of these bits,
      so fix all uses (and former uses) to check for any non-zero value.
      Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      b3e338de
  2. 07 1月, 2011 2 次提交
  3. 05 1月, 2011 2 次提交
  4. 22 10月, 2010 2 次提交
  5. 30 9月, 2009 1 次提交
  6. 27 1月, 2009 1 次提交
    • S
      m68knommu: use one exist from execption · c7bcd0df
      Sebastian Siewior 提交于
      Part of the code that did not make sense to me got removed by Greg.
      This is part two:
      
      The first compare is to check whether the interrupts are disabled or not.
      Depending on the result we exectute the RESTORE_ALL macro is not only
      restoring the stack but also returning to caller.
      The test for pending softirq has been removed because it is allready done
      in irq_exit().
      Since system_call() is allso using the SAVE_ALL macro and returning via
      ret_from_exception label I see no reason why we could not do this here
      as well. This is also handy because if we return from the timer interrupt
      and we need to resched than we check for this :)
      Signed-off-by: NSebastian Siewior <bigeasy@linutronix.de>
      Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      c7bcd0df
  7. 01 5月, 2008 2 次提交
  8. 15 2月, 2008 1 次提交
  9. 01 2月, 2008 1 次提交
  10. 23 10月, 2007 1 次提交
  11. 26 7月, 2007 1 次提交
  12. 20 7月, 2007 1 次提交
  13. 01 7月, 2006 1 次提交
  14. 26 6月, 2006 1 次提交
  15. 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